[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN107426150B - Method and system for monitoring and replacing user nickname - Google Patents

Method and system for monitoring and replacing user nickname Download PDF

Info

Publication number
CN107426150B
CN107426150B CN201710207902.6A CN201710207902A CN107426150B CN 107426150 B CN107426150 B CN 107426150B CN 201710207902 A CN201710207902 A CN 201710207902A CN 107426150 B CN107426150 B CN 107426150B
Authority
CN
China
Prior art keywords
user
nickname
reserved
registered
abnormal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710207902.6A
Other languages
Chinese (zh)
Other versions
CN107426150A (en
Inventor
姚金明
张文明
陈少杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Gaosheng Jiangsu Technology Co ltd
Original Assignee
Wuhan Douyu Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Wuhan Douyu Network Technology Co Ltd filed Critical Wuhan Douyu Network Technology Co Ltd
Priority to CN201710207902.6A priority Critical patent/CN107426150B/en
Publication of CN107426150A publication Critical patent/CN107426150A/en
Application granted granted Critical
Publication of CN107426150B publication Critical patent/CN107426150B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00Indexing scheme associated with group H04L61/00
    • H04L2101/30Types of network names
    • H04L2101/365Application layer names, e.g. buddy names, unstructured names chosen by a user or home appliance name
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/30Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015Name registration, generation or assignment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/30Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015Name registration, generation or assignment
    • H04L61/302Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Computer And Data Communications (AREA)

Abstract

The invention discloses a method and a system for monitoring and replacing a nickname of a user, and relates to the field of network registration keyword monitoring. The method comprises the following steps: the server sets a user reserved nickname periodically; after receiving the nickname of the user registered by the client to which the user belongs, the server judges whether the nickname of the user is the same as the nickname reserved by the user, and if so, returns registration success information to the client to which the user belongs; otherwise, returning registration abnormal information to the client to which the user belongs; after the server side obtains the preset user reserved nicknames, when the registered user nicknames are traversed in the user reserved nicknames, the server side marks the current registered user nicknames as the nicknames of the abnormal users, and when the abnormal users log in, the server side returns the registration abnormal information to the client side to which the abnormal users belong. The invention can accurately monitor the nickname of the registered user, and ensures that the nickname of the registered user does not belong to the reserved nickname of the user, thereby effectively ensuring the benefit of the user and being very suitable for popularization.

Description

Method and system for monitoring and replacing user nickname
Technical Field
The invention relates to the field of network registration keyword monitoring, in particular to a method and a system for monitoring and replacing a nickname of a user.
Background
When people watch or host the network live broadcast, the people can register the nicknames of the users in the related websites of the network live broadcast room; with the rapid development of the network live broadcast industry, the number of users (anchor and audience) of the network live broadcast is increased, and the number of network nicknames registered by the users is increased. Since each user nickname is unique, it is necessary to modify the nickname of the subsequently registered user when the nickname of the subsequently registered user is identical to the nickname of the previously registered user.
However, in consideration of the rapid propagation of the network information, it may happen that the nickname of the previously registered user is actually third-party information (e.g., information of another person or illegal words, that is, "pseudo-user nickname") that does not correspond to the user, and at this time, when the third-party user is registered, the corresponding third-party information cannot be registered, so that the nickname of the user cannot be correctly identified, and the safety of the third party may be seriously damaged. For example, Zhang III knows that the term "Liqu" is commercially valuable, and thus "Liqu" is preempted as a user nickname to impersonate real Liqu, while Liqu is informed that the user nickname "Liqu" is registered at the time of registration, and other user nicknames need to be used.
Currently, some websites use a real-name authentication method to mark a nickname of a user registered later, that is, use an official mark method to authenticate a "real" user whose nickname does not correspond to the user. However, the above-mentioned real-name authentication method cannot eliminate the adverse effect of the previously registered "pseudo user nickname".
Disclosure of Invention
Aiming at the defects in the prior art, the invention solves the technical problems that: how to prevent the nickname of the registered user from containing abnormal information. The invention can accurately monitor the nickname of the registered user, and ensures that the nickname of the registered user does not belong to the reserved nickname of the user, thereby effectively ensuring the benefit of the user and being very suitable for popularization.
In order to achieve the above purpose, the method for monitoring and replacing the nickname of the user provided by the invention comprises the following steps:
step A: b, the server sets a user reserved nickname regularly, the regular period is 1-5 days, and the step B is carried out;
and B: after receiving the nickname of the user registered by the client to which the user belongs, the server judges whether the nickname of the user is the same as the nickname reserved by the user, and if so, returns registration success information to the client to which the user belongs; otherwise, returning registration abnormal information to the client to which the user belongs, and ending;
step A is followed by step C: after the server side obtains the preset nicknames of all users, judging whether the registered nicknames of the users are traversed in the preset nicknames of all the users, if so, turning to the step D, otherwise, ending;
step D: and the server marks the current registered user nickname as the abnormal user nickname, and when the abnormal user logs in, returns the abnormal registration information to the client to which the abnormal user belongs, and ends.
The invention provides a monitoring and replacing system for a user nickname, which comprises a user reserved nickname setting module, a user nickname registration monitoring module, a user nickname searching module and an abnormal user nickname marking module, wherein the user reserved nickname setting module, the user nickname registration monitoring module, the user nickname searching module and the abnormal user nickname marking module are positioned at a service end;
the user reserved nickname setting module is used for: regularly setting a user reserved nickname, wherein the regular period is 1-5 days, and sending a user nickname searching signal to a user nickname searching module;
the user nickname registration monitoring module is used for: after receiving the nickname of the user registered by the client side to which the user belongs, the server side judges whether the nickname of the user is the same as the nickname reserved by the user set by the nickname reservation setting module, and if so, returns registration success information to the client side to which the user belongs; otherwise, returning registration abnormal information to the client to which the user belongs;
the user nickname checking module is used for: after receiving a user nickname searching signal, acquiring all set user reserved nicknames, and sending an abnormal user nickname marking signal to an abnormal user nickname marking module when the registered user nicknames are traversed in all user reserved nicknames;
the abnormal user nickname marking module is used for: and after receiving the nickname marking signal of the abnormal user, marking the current registered nickname of the user as the nickname of the abnormal user, and returning registration abnormal information to the client side to which the abnormal user belongs when the abnormal user logs in.
Compared with the prior art, the invention has the advantages that:
(1) it can be known from the step a and the step B of the present invention that the present invention compares the registered user nickname with the preset user reserved nickname, and when the registered user nickname is the same as the user reserved nickname, the user nickname is prohibited from being registered (i.e., registration exception information is returned to the client). Therefore, the invention can accurately monitor the nickname of the registered user, ensures that the nickname of the registered user does not belong to the nickname reserved by the user, avoids the nickname of a pseudo user in the prior art, further effectively ensures the benefit of the user and is very suitable for popularization.
On the basis, referring to the step C and the step D of the invention, the invention can immediately monitor the registered user nickname after setting the new user reserved nickname, eliminate the registered user nickname, belong to the situation that the user reserved nickname is set after the registration time, and further ensure the benefits of the user. For example: zhang III knows that the term "Li four" has high commercial value, so that the name "Li four" is taken as the nickname of the registered user, but the nickname reserved by the user does not have the name "Li four", and after the nickname reserved for the user by the user is set at the later stage, Zhang III modifies the nickname of the registered user to ensure the benefit of the real user Li four.
(2) Before comparing the registered user nickname with the user reserved nickname, the invention firstly carries out primary monitoring on the registered user nickname: and judging whether the registered user nickname is the same as the registered user nickname, if so, registering the user nickname, and directly ending without performing subsequent processes so as to achieve the aims of improving the working efficiency and reducing the operation cost.
(3) When the nickname of the user is the same as the registered nickname of the user, the invention returns the registration failure information; and when the nickname of the user is the same as the reserved nickname of the user, returning abnormal registration information. The registration failure information and the registration abnormal information respectively inform the user of specific reasons when the registration is unsuccessful, so that the user can know that the application of the invention has the function of monitoring the nickname of the user and stipulates the nickname details of the user which cannot be registered, the user can conveniently and pointedly modify the nickname of the registered user according to the specific registration failure or abnormal information, the user experience is improved, and the propaganda and popularization strength of the invention is also improved.
(4) The invention sets the regular period of the user reserved nickname as 1 day, namely, the user reserved nickname is set every day and the registered user nickname is monitored, the monitoring period is shorter, and the monitoring precision is obviously improved.
Drawings
FIG. 1 is a flowchart of an alternative method for monitoring a nickname of a user in an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples.
Referring to fig. 1, the method for monitoring and replacing the nickname of the user in the embodiment of the present invention includes the following steps:
s1: in order to monitor whether the registered or used user nickname is abnormal in real time, the server needs to regularly (1-5 days) set a user reserved nickname, the user reserved nickname comprises keywords and/or symbols, the keywords comprise Chinese and/or English, and the realization mode is as follows: and the background server adds the user reserved nickname to the user nickname reservation server in a newly added mode, and the S2 is switched to.
S2: and after receiving the nickname registered by the client side to which the user belongs, the server side acquires the user reserved nickname through the registration interface, judges whether the current registered user nickname is the same as the registered user nickname, returns registration failure information (the same user nickname is registered) to the client side to which the user belongs if the current registered user nickname is the same as the registered user nickname, and ends the process, otherwise, the process goes to S3.
The purpose of S2 is: and primary monitoring is carried out on the registered user nickname, and if the user nickname is registered, subsequent processes are not required to be carried out, and the process is directly finished, so that the working efficiency is improved, and the operation cost is reduced.
S3: the server side starts the reserved user nickname service: the background server (WebMasterServer) sets the State of the user nickname reservation service to be Open (Open) through a control parameter (State):
set webmasterserver. nicknamefunction. state (Open), go to S4.
S4: the server side obtains the user reserved nickname through the registration interface, judges whether the registered user nickname is the same as the user reserved nickname or not, if so, returns registration success information to the client side to which the user belongs, and then goes to S5, otherwise, returns registration abnormal information to the client side to which the user belongs (the currently registered user nickname is unavailable, and the user can freely modify the user nickname at this moment), and the process is finished.
The registration failure information in the S2 and the registration exception information in the S4 respectively inform the user of a specific reason when the registration is unsuccessful, so that the user can know that the website adopting the embodiment has a function of monitoring the nickname of the user and specifies the nickname details of the user who cannot be registered, and the user can modify the nickname of the registered user in a targeted manner according to the specific registration failure or exception information, thereby improving the user experience and promoting the promotion and popularization of the website.
The purpose of S4 is: the nicknames of the registered users are accurately monitored, the nicknames of the registered users are guaranteed not to belong to the nicknames reserved by the users, the nicknames of 'pseudo users' in the prior art are avoided, the benefits of the users are further guaranteed, and the method is very suitable for popularization.
The specific process of S4 is as follows: the front-end server sends the registered user nickname to a verification interface provided by the user nickname reservation server for requesting in a parameter mode through an external registration interface. After the request is successful, judging the returned result of the request, if the returned result is 1, the nickname of the user is the same as the reserved nickname of the user, at the moment, returning registration failure information to the client to which the user belongs, and ending; if the returned result is null, the nickname of the user is different from the nickname reserved by the user, and at this time, registration success information is returned to the client to which the user belongs, and the process goes to S5.
S5: and calling an opening parameter (State) through the background server to open a user reserved nickname scanning function (Scanning function):
set webmasterserver.scanning function.state (Open), go to S6.
S6: and the server side acquires all the user reserved nicknames set in the S1, judges whether the registered user nicknames are traversed in all the user reserved nicknames, if so, turns to S7, and otherwise, ends.
The purpose of S6 is: after the new user reserved nickname is set in S1, the registered user nickname is monitored immediately, the registered user nickname is excluded, and the user reserved nickname set after the registration time is the subject, so that the benefit of the user is further ensured. For example: zhang III knows that the term "Li four" has high commercial value, so that the name "Li four" is taken as the nickname of the registered user, but the nickname reserved by the user does not have the name "Li four", and after the nickname reserved for the user by the user is set to be the nickname in the later period, Zhang III can modify the nickname "Li four" of the registered user to ensure the benefit of the user Li four. In practical applications, S6 may be concurrent with any flow after S1, and the periodic period in S1 is 1 day, and the shorter the periodic period, the higher the monitoring accuracy, in view of the work efficiency and the work cost.
The specific flow of S6 is as follows: forming a comparison set by all the user reserved nicknames set in the S1 through accessing a user nickname query interface externally provided by the background server; and acquiring the registered user nickname through a user nickname query interface of the background server. Judging whether the registered user nickname is traversed in the comparison set, if so, turning to S7; otherwise, ending.
S7: and marking the nickname of the currently registered user as the nickname of the abnormal user, returning registration abnormal information to the client side to which the abnormal user belongs when the abnormal user logs in (the nickname of the currently registered user is unavailable, and the nickname of the user can be freely modified by the user at the moment), and ending.
The monitoring and replacing system for the user nickname in the embodiment of the invention comprises a user reserved nickname setting module, a user nickname registration monitoring module, a user nickname searching module and an abnormal user nickname marking module which are positioned at a service end.
The user reserved nickname setting module is used for: regularly setting a nickname reserved by a user, wherein the regular period is 1-5 days (in the embodiment, 1 day), the nickname reserved by the user comprises keywords and/or symbols, and the keywords comprise Chinese and/or English; and sending a user nickname checking signal to the user nickname checking module.
The user nickname registration monitoring module is used for: after receiving the nickname of the user registered by the client to which the user belongs, the server judges whether the nickname of the currently registered user is the same as the nickname of the registered user, if so, the server returns registration failure information (the nickname of the same user is registered) to the client to which the user belongs, and terminates the subsequent process; otherwise:
judging whether the nickname of the user is the same as the user reserved nickname set by the user reserved nickname setting module, if so, returning registration success information to the client to which the user belongs; otherwise, returning abnormal registration information (the nickname of the currently registered user is unavailable) to the client to which the user belongs.
The user nickname checking module is used for: after receiving the user nickname searching signal, acquiring the set reserved nicknames of all users, and sending an abnormal user nickname marking signal to the abnormal user nickname marking module when the registered user nicknames are traversed in the reserved nicknames of all users.
The abnormal user nickname marking module is used for: and after receiving the nickname marking signal of the abnormal user, marking the current registered nickname of the user as the nickname of the abnormal user, and returning registration abnormal information to the client side to which the abnormal user belongs when the abnormal user logs in.
The embodiment of the invention can accurately monitor the nickname of the registered user, ensure that the nickname of the registered user does not belong to the nickname reserved by the user, avoid the nickname of a pseudo user in the prior art, and monitor the nickname of the registered user immediately after the nickname reserved by the new user is set, so as to eliminate the nickname of the registered user and belong to the situation that the nickname reserved by the user is set after the registration time. Therefore, the invention effectively ensures the benefits of users and is very suitable for popularization.
Further, the present invention is not limited to the above-mentioned embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and these modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.

Claims (10)

1. A method for monitoring and replacing a nickname of a user is characterized by comprising the following steps:
step A: b, the server sets a user reserved nickname regularly, the regular period is 1-5 days, and the step B is carried out;
and B: after receiving the nickname of the user registered by the client to which the user belongs, the server judges whether the nickname of the user is the same as the nickname reserved by the user, if so, returns registration abnormal information to the client to which the user belongs, and ends; otherwise, returning registration success information to the client to which the user belongs, and ending;
step A is followed by step C: after the server side obtains the preset nicknames of all users, judging whether the registered nicknames of the users are traversed in the preset nicknames of all the users, if so, turning to the step D, otherwise, ending;
step D: and the server marks the current registered user nickname as the abnormal user nickname, and when the abnormal user logs in, returns the abnormal registration information to the client to which the abnormal user belongs, and ends.
2. A method of monitoring substitution of a user nickname as recited in claim 1, wherein: before the step B of judging whether the nickname of the user is the same as the nickname reserved by the user, the method further comprises the following steps: judging whether the nickname of the currently registered user is the same as the nickname of the registered user, if so, returning registration failure information to the client to which the user belongs, and terminating the subsequent flow; otherwise, continuing the subsequent flow.
3. The method of claim 2, wherein the registration failure information is: the nicknames of the same users are registered; the abnormal registration information in the step B and the step D is as follows: the nickname of the currently registered user is not available.
4. A method of monitoring substitution of a nickname for a user according to any one of claims 1 to 3, wherein: the nickname reserved by the user in the step A comprises keywords and/or symbols, and the keywords comprise Chinese and/or English.
5. A method of monitoring substitution of a nickname for a user according to any one of claims 1 to 3, wherein: the periodic period in step a is 1 day.
6. A system for monitoring and replacing nicknames of users, comprising: the system comprises a user reserved nickname setting module, a user nickname registration monitoring module, a user nickname searching module and an abnormal user nickname marking module which are positioned at a service end;
the user reserved nickname setting module is used for: regularly setting a user reserved nickname, wherein the regular period is 1-5 days, and sending a user nickname searching signal to a user nickname searching module;
the user nickname registration monitoring module is used for: after receiving the nickname of the user registered by the client side to which the user belongs, the server side judges whether the nickname of the user is the same as the nickname reserved by the user set by the nickname reservation setting module, if so, the server side returns registration abnormal information to the client side to which the user belongs, and the process is finished; otherwise, returning registration success information to the client to which the user belongs, and ending;
the user nickname checking module is used for: after receiving a user nickname searching signal, acquiring all set user reserved nicknames, and sending an abnormal user nickname marking signal to an abnormal user nickname marking module when the registered user nicknames are traversed in all user reserved nicknames;
the abnormal user nickname marking module is used for: and after receiving the nickname marking signal of the abnormal user, marking the current registered nickname of the user as the nickname of the abnormal user, and returning registration abnormal information to the client side to which the abnormal user belongs when the abnormal user logs in.
7. The system for monitoring substitution of a nickname for a user of claim 6, wherein: before the user nickname registration monitoring module judges whether the nickname of the user is the same as the nickname reserved by the user, the user nickname registration monitoring module also judges whether the current registered user nickname is the same as the registered user nickname, if so, registration failure information is returned to a client side to which the user belongs, and the subsequent process is terminated; otherwise, continuing the subsequent flow.
8. The system for monitoring substitution of a nickname for a user of claim 7, wherein: the registration failure information is: the nicknames of the same users are registered; the registration exception information returned to the client by the user nickname registration monitoring module and the abnormal user nickname marking module is as follows: the nickname of the currently registered user is not available.
9. The system of any one of claims 6 to 8, wherein the nickname monitoring system is further configured to: the user reserved nickname set by the user reserved nickname setting module comprises keywords and/or symbols, and the keywords comprise Chinese and/or English.
10. The system of any one of claims 6 to 8, wherein the nickname monitoring system is further configured to: the user reserved nickname setting module sets the regular period of the user reserved nicknames to be 1 day.
CN201710207902.6A 2017-03-31 2017-03-31 Method and system for monitoring and replacing user nickname Active CN107426150B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710207902.6A CN107426150B (en) 2017-03-31 2017-03-31 Method and system for monitoring and replacing user nickname

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710207902.6A CN107426150B (en) 2017-03-31 2017-03-31 Method and system for monitoring and replacing user nickname

Publications (2)

Publication Number Publication Date
CN107426150A CN107426150A (en) 2017-12-01
CN107426150B true CN107426150B (en) 2020-09-04

Family

ID=60423218

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710207902.6A Active CN107426150B (en) 2017-03-31 2017-03-31 Method and system for monitoring and replacing user nickname

Country Status (1)

Country Link
CN (1) CN107426150B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101184082A (en) * 2006-11-17 2008-05-21 华为技术有限公司 Cluster user login method, state updating method, processing equipment, IMS network entity and communication system
CN101316262A (en) * 2007-05-31 2008-12-03 中兴通讯股份有限公司 Method for controlling repeated registration of the same account terminal
CN103118043A (en) * 2011-11-16 2013-05-22 阿里巴巴集团控股有限公司 Identification method and equipment of user account

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160359779A1 (en) * 2015-03-16 2016-12-08 Boogoo Intellectual Property LLC Electronic Communication System

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101184082A (en) * 2006-11-17 2008-05-21 华为技术有限公司 Cluster user login method, state updating method, processing equipment, IMS network entity and communication system
CN101316262A (en) * 2007-05-31 2008-12-03 中兴通讯股份有限公司 Method for controlling repeated registration of the same account terminal
CN103118043A (en) * 2011-11-16 2013-05-22 阿里巴巴集团控股有限公司 Identification method and equipment of user account

Also Published As

Publication number Publication date
CN107426150A (en) 2017-12-01

Similar Documents

Publication Publication Date Title
US20170331834A1 (en) Centralized authentication for granting access to online services
CN104580085B (en) service data updating method, system, client and server
CN105142146B (en) Authentication method, device and system for WIFI hotspot access
CN111314285B (en) Method and device for detecting route prefix attack
US20190014532A1 (en) Adss enabled global roaming system
WO2009085629A4 (en) Wireless device authentication using digital certificates
US20180091355A1 (en) Single sign-on system and single sign-on method
CN106656998B (en) server communication method and device
CN108023881B (en) Application login method, device, medium and electronic equipment
CN105100041B (en) Communicator, the control method of communicator and printer
CN109246078B (en) Data interaction method and server
JP2008242644A (en) User authentication system using position information
CN102098659A (en) Method and system for fast verifying international mobile equipment identity (IMEI)
CN108282843B (en) Network query method, device and server
CN107959920B (en) Wireless network-based sign-in method and equipment
CN106899651B (en) Communication processing method, system and network communication system
KR20150099425A (en) Network system for retrieval of configuration related data
CN104994501A (en) Connection method of wireless network and terminal equipment
CN107426150B (en) Method and system for monitoring and replacing user nickname
CN111064729B (en) Message processing method and device, storage medium and electronic device
CN109462589B (en) Method, device and equipment for controlling network access of application program
KR101380041B1 (en) Automatic login system and method that use portable terminal
CN109905243B (en) Method and server for processing digital certificate updating request
CN107766212B (en) Method and device for determining installation state of application program
WO2020024402A1 (en) Traffic feature management method and apparatus, and central node server

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20230512

Address after: 224100 North of Jinsu Road, Dafenggang Economic Zone, Dafeng District, Yancheng City, Jiangsu Province, and the third floor of Suyan Park Management Committee, west of Second Industrial Avenue

Patentee after: Jiangsu Yihui Jimou Technology Co.,Ltd.

Address before: 510000 2414-2416 of the main building 371, five mountain road, Tianhe District, Guangzhou, Guangdong.

Patentee before: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd.

Effective date of registration: 20230512

Address after: 510000 2414-2416 of the main building 371, five mountain road, Tianhe District, Guangzhou, Guangdong.

Patentee after: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd.

Address before: 430000 East Lake Development Zone, Wuhan City, Hubei Province, No. 1 Software Park East Road 4.1 Phase B1 Building 11 Building

Patentee before: WUHAN DOUYU NETWORK TECHNOLOGY Co.,Ltd.

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20231220

Address after: 309-4, Building 2, No. 379, Tayuan Road, High tech Zone, Suzhou City, Jiangsu Province, 215000

Patentee after: Gaosheng (Jiangsu) Technology Co.,Ltd.

Address before: 224100 North of Jinsu Road, Dafenggang Economic Zone, Dafeng District, Yancheng City, Jiangsu Province, and the third floor of Suyan Park Management Committee, west of Second Industrial Avenue

Patentee before: Jiangsu Yihui Jimou Technology Co.,Ltd.