CN110557396B - Method and system for unifying login sessions between H5 clients - Google Patents
Method and system for unifying login sessions between H5 clients Download PDFInfo
- Publication number
- CN110557396B CN110557396B CN201910847279.XA CN201910847279A CN110557396B CN 110557396 B CN110557396 B CN 110557396B CN 201910847279 A CN201910847279 A CN 201910847279A CN 110557396 B CN110557396 B CN 110557396B
- Authority
- CN
- China
- Prior art keywords
- client
- login
- session
- channel number
- session information
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
Abstract
The invention discloses a method for unifying login sessions between H5 clients, which comprises the following steps: receiving a call request sent by a logged-in first client, inquiring whether login session information of a second client exists in a session storage object, and if so, setting the second client to be in a login state; and receiving a service request sent by the called second client, wherein the service request comprises the channel number of the first client, refreshing calling session information by adopting the channel number of the first client, returning the refreshed calling session information to the first client, and returning service data to the second client. The invention can directly call the client without inputting login information, thereby reducing the operation amount of the user; by setting the channel number for each client, the channel number of the client initiating the call is adopted to continuously refresh the session information in the call process, so as to ensure the sharing and maintenance of the login session and avoid the client initiating the call from entering the session overtime state due to long-time lost operation.
Description
Technical Field
The invention relates to the technical field of client calling, in particular to a method and a system for unifying login sessions between H5 clients.
Background
At present, the H5 client A calls another H5 client B, and the called client B needs to input corresponding login information again to be called formally, so that the operation of a user is quite inconvenient.
In addition, if the user operates the called client B for a long time, since the client a initiating the call request cannot obtain the operation information in this period, when the user switches back to the client a, the session of the client a is already over time, and the user needs to perform the operation again.
Disclosure of Invention
The invention aims to provide a method and a system for unifying login sessions between H5 clients, wherein login information of each client is stored in sessionStorage, and when any client is called, if the corresponding login information exists in the sessionStorage, the login state is directly switched to, so that the user operation amount is reduced; in addition, a channel number is set for each client, the channel number of the client initiating the call is the channel number of the whole life cycle in the process of one call, and the called client continuously refreshes session information by adopting the channel number of the client initiating the call in the operation process so as to ensure the sharing and maintenance of the login session and avoid entering a session overtime state due to long-time lost operation after the called client is operated for a long time.
To achieve the above object, with reference to fig. 1, the present invention provides a method for unifying login sessions between H5 clients, where all H5 clients are deployed in the same domain, and store respective login session information through a session storage object;
the method comprises the following steps:
s1: receiving a login request sent by a first client, wherein the login request comprises a channel number of the first client, generating real-time session information, returning the real-time session information to the first client, and storing the channel number of the first client to a session storage object;
s2: in response to receiving a call request for a second client sent by a first client, querying whether login session information of the second client exists from a session storage object, if so, setting the second client to be in a login state, and entering a step S3, otherwise, ending the process;
s3: and receiving a service request sent by the called second client, wherein the service request comprises the channel number of the first client, refreshing the real-time session information by adopting the channel number of the first client, returning the refreshed real-time session information to the first client, and simultaneously returning service data to the second client.
In a further embodiment, the method further comprises:
and receiving service requests sent by different clients, wherein the service requests comprise client identifiers of corresponding clients, and returning the requested service data to the corresponding clients according to the client identifiers.
In a further embodiment, a unified session management center is employed to uniformly manage session information for all H5 clients.
In a further embodiment, the method further comprises:
and taking the pathname acquired by adopting a hash routing mode as the client identifier.
Based on the method, the invention also provides a system for unifying login sessions between H5 clients, which is suitable for unifying login session information of a first client and a second client when the first client which has logged in calls the second client, and comprises a unified session management center, a first service server, a second service server and a session storage object;
the session storage object is used for storing login session information of different clients;
the first service server is used for receiving a login request sent by a first client, wherein the login request comprises a channel number of the first client, sending the login request to the unified session management center to acquire real-time session information returned by the unified session management center, returning the real-time session information to the first client, and storing the channel number of the first client into a session storage object;
the second client responds to the call of the first client, inquires whether corresponding login session information exists in the session storage object, if not, the call process is ended, otherwise, the second client is directly switched to a login state, and
and sending the received service request to a second service server, wherein the service request comprises the channel number of the first client acquired from the session storage object, and the second service server adopts the channel number of the first client to interact with the unified session management center so as to refresh the real-time session information sent to the first client by the unified session management center, and simultaneously returns the service data to the second client.
In a further embodiment, the unified session management center is further configured to receive a call request sent by any one of the clients, where the call request includes the channel number of the client, return call session information to the corresponding client, and store the channel number of the client in the session storage object.
In a further embodiment, the system further comprises a general purpose server;
the universal server is used for receiving service requests sent by different clients, the service requests comprise client identifiers of corresponding clients, and the requested service data are returned to the corresponding clients according to the client identifiers.
Compared with the prior art, the technical scheme of the invention has the following remarkable beneficial effects:
(1) and storing the login information of each client in the sessionStorage, and directly switching to a login state if the corresponding login information exists in the sessionStorage when any client is called, so that the user operation amount is reduced.
(2) Setting a channel number for each client, wherein in a calling process, the channel number of the client initiating the calling is the channel number of the whole life cycle, and the called client continuously refreshes real-time session information by adopting the channel number of the client initiating the calling in an operation process so as to ensure the sharing and maintenance of login sessions and avoid that the client initiating the calling enters a session overtime state due to long-time loss of operation after the client is called for long time operation
(3) And setting a client identifier for each client so as to effectively distinguish different clients on the basis of unifying channel numbers.
(4) Considering that the corresponding back-end servers of each client may be different, a unified session management center is adopted to uniformly manage the session information of all the clients in the calling process.
It should be understood that all combinations of the foregoing concepts and additional concepts described in greater detail below can be considered as part of the inventive subject matter of this disclosure unless such concepts are mutually inconsistent. In addition, all combinations of claimed subject matter are considered a part of the presently disclosed subject matter.
The foregoing and other aspects, embodiments and features of the present teachings can be more fully understood from the following description taken in conjunction with the accompanying drawings. Additional aspects of the present invention, such as features and/or advantages of exemplary embodiments, will be apparent from the description which follows, or may be learned by practice of specific embodiments in accordance with the teachings of the present invention.
Drawings
The drawings are not intended to be drawn to scale. In the drawings, each identical or nearly identical component that is illustrated in various figures may be represented by a like numeral. For purposes of clarity, not every component may be labeled in every drawing. Embodiments of various aspects of the present invention will now be described, by way of example, with reference to the accompanying drawings, in which:
fig. 1 is a flow chart of the method for unifying login sessions between H5 clients of the present invention.
Fig. 2 is an information transmission flowchart of a specific example of the present invention.
Detailed Description
In order to better understand the technical content of the present invention, specific embodiments are described below with reference to the accompanying drawings.
With reference to fig. 1, the present invention provides a method for unifying login sessions between H5 clients, where all H5 clients are deployed in the same domain, and store respective login session information through a session storage object.
The method comprises the following steps:
s1: receiving a login request sent by a first client, wherein the login request comprises a channel number of the first client, generating real-time session information, returning the real-time session information to the first client, and storing the channel number of the first client to a session storage object.
S2: and responding to a received call request for the second client sent by the first client, inquiring whether login session information of the second client exists in the session storage object, if so, setting the second client to be in a login state, and entering the step S3, otherwise, ending the flow.
S3: and receiving a service request sent by the called second client, wherein the service request comprises the channel number of the first client, refreshing the real-time session information by adopting the channel number of the first client, returning the refreshed real-time session information to the first client, and simultaneously returning service data to the second client.
Because all the clients are deployed in the same domain and the login information is stored in the sessionStorage, when any client is called, if the corresponding login information exists in the sessionStorage, the login state is directly switched to, and the user operation amount is reduced.
In connection with fig. 2, for example, there are client a and client B in the same domain, each client having a unique channel number and a unique client identifier. Suppose that the channel number corresponding to the client a is channel a, the client identifier is clientA, the channel number corresponding to the client B is channel B, and the client identifier is clientB. Preferably, the method further comprises: and taking the pathname acquired by adopting a hash routing mode as the client identifier. For example http: 127.0.0.1/clientA/#/routerPath.
The client A and the client B both store the login information of the client A and the client B in sessionStorage, and when the client B is called by the client A, the client B considers that the current login state is the current login state as long as the client B takes the corresponding login session information in the sessionStorage.
The channel number of the first started client is the channel number of the whole life cycle, and at this time, if the client calls other clients, the channel numbers corresponding to the other clients are also the channel numbers of the first started client.
For example, after the client a is started, the channel number of the client a is stored in the sessionStorage, then the client a calls the client B, and the client B interacts with the backend through the channel number of the client a stored in the sessionStorage and the client identifier clientB of the client B, where the former is used to indicate the called relationship and the latter is used to indicate the identity of the client. The back end generates corresponding session information according to the channel number, and can know who the client calling the service request is for the client identification.
Specifically, after receiving a service request initiated by the client B, the back end takes the channel number channelA of the client a, which is transmitted by the client B, to refresh the session, so that sharing and maintenance of the login session are ensured, and each service request of the client B refreshes the operation state of the client a in addition to the own operation state. Therefore, the problem that the operation session information displayed by the client A is overtime when the client B enters the client A again due to long-time operation does not exist.
Considering that the backend services corresponding to each client may be different, for example, the client a corresponds to the server a, and the client B corresponds to the server B, there is a possibility that the respective services process respective session information, which makes it difficult to keep the session information consistent in the calling process. At this time, a unified session management center can be set, the unified session management center is adopted to maintain all client session information, and a session information acquisition, query and refresh interface is provided for the outside, so as to solve the problems.
Based on the method, the invention also provides a system for unifying login sessions between H5 clients, which is suitable for unifying login session information of a first client and a second client when the first client which has logged in calls the second client.
The session storage object is used for storing login session information of each client, the login session information can be directly stored in the session storage object after the client logs in, and the login session information of the corresponding client can be uniformly returned through the uniform session management center. For example:
the first service server corresponds to the first client and is used for receiving the login request sent by the first client, sending the login request to the unified session management center so as to obtain login session information of the first client returned by the unified session management center, and storing the login session information of the first client into the session storage object. Similarly, the second service server corresponds to the second client, and is configured to receive a login request sent by the second client, send the login request to the unified session management center, so as to obtain login session information of the second client returned by the unified session management center, and store the login session information of the second client in the session storage object.
Because there is a call relationship between the first client and the second client, in practical applications, only one client usually sends a login request to the unified session management center. For example, after the client a is started, a login request is sent to the corresponding server a, the login request includes the channel number channel a of the client a, the server a sends the login request to the unified session center, the unified session center returns login session information to the server a, the server a sends the login session information to the client a, and the channel number channel a of the client a is stored in the session storage object.
The step of the channel number channel a of the client a to the session storage object may be performed when the client a issues a call request, and only the login session information may be stored in the session storage object at the time of login.
For example, the unified session management center receives a call request sent by the client a and forwarded by the server a, the call request includes a channel number channelA of the client a, call session information is returned to the client a, and the channel number channelA of the client a is stored in a session storage object for the called client B to call.
The second client responds to the call of the first client, inquires whether corresponding login session information exists in the session storage object, if not, the call process is ended, otherwise, the second client is directly switched to a login state, and
and sending the received service request to a second service server, wherein the service request comprises the channel number of the first client, and the second service server adopts the channel number of the first client to interact with the unified session management center so as to refresh the real-time session information sent to the first client by the unified session management center, and simultaneously returns the service data to the second client.
After a first started client A logs in, a channel number channel A is transmitted; the client A calls the client B, the client B requests service data, the service request comprises a channel number channelA, the server B refreshes the session firstly, and then the service data is returned.
If the two clients relate to the same universal server, the universal server respectively processes the corresponding service requests according to client identifiers (for example, the client identifier of the client A is clientA, and the client identifier of the client B is clientB) contained in the service requests.
In this disclosure, aspects of the present invention are described with reference to the accompanying drawings, in which a number of illustrative embodiments are shown. Embodiments of the present disclosure are not necessarily defined to include all aspects of the invention. It should be appreciated that the various concepts and embodiments described above, as well as those described in greater detail below, may be implemented in any of numerous ways, as the disclosed concepts and embodiments are not limited to any one implementation. In addition, some aspects of the present disclosure may be used alone, or in any suitable combination with other aspects of the present disclosure.
Although the present invention has been described with reference to the preferred embodiments, it is not intended to be limited thereto. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the invention. Therefore, the protection scope of the present invention should be determined by the appended claims.
Claims (7)
1. A unified method for login sessions among H5 clients is characterized in that all H5 clients are deployed in the same domain, and respective login session information is stored through a session storage object;
the method comprises the following steps:
s1: receiving a login request sent by a first client, wherein the login request comprises a channel number of the first client, generating real-time session information, returning the real-time session information to the first client, and storing the channel number of the first client to a session storage object;
s2: in response to receiving a call request for a second client sent by a first client, querying whether login session information of the second client exists from a session storage object, if so, setting the second client to be in a login state, and entering a step S3, otherwise, ending the process;
s3: receiving a service request sent by a called second client, wherein the service request comprises a channel number of the first client, refreshing real-time session information by adopting the channel number of the first client, returning the refreshed real-time session information to the first client, and simultaneously returning service data to the second client;
in the process of one-time calling, the channel number of the first client initiating the calling is the channel number of the whole life cycle, the channel number of the first client is taken as the channel number of the second client during the operation process of the called second client, and the channel number of the first client is adopted to continuously refresh the session information.
2. The method for unifying login sessions between H5 clients according to claim 1, further comprising:
and receiving service requests sent by different clients, wherein the service requests comprise client identifiers of corresponding clients, and returning the requested service data to the corresponding clients according to the client identifiers.
3. The method for unifying login sessions between H5 clients according to claim 1, wherein a unified session management center is adopted to manage the session information of all H5 clients in a unified manner.
4. The method for unifying login sessions between H5 clients according to claim 1, further comprising:
and taking the pathname acquired by adopting a hash routing mode as the client identifier.
5. A unified system of login session between H5 clients is suitable for unifying login session information of a first client and a second client when the first client which has logged in calls the second client, and is characterized in that the system comprises a unified session management center, a first service server, a second service server and a session storage object;
the session storage object is used for storing login session information of different clients;
the first service server is used for receiving a login request sent by a first client, wherein the login request comprises a channel number of the first client, sending the login request to the unified session management center to acquire real-time session information returned by the unified session management center, returning the real-time session information to the first client, and storing the channel number of the first client into a session storage object;
the second client-side responds to the calling by the first client-side, whether the login session information of the second client-side exists or not is inquired from the session storage object, if the login session information does not exist, the calling process is ended, otherwise, the second client-side is directly switched to the login state, and
and sending the received service request to a second service server, wherein the service request comprises the channel number of the first client acquired from the session storage object, and the second service server adopts the channel number of the first client to interact with the unified session management center so as to refresh the real-time session information sent to the first client by the unified session management center, and simultaneously returns the service data to the second client.
6. The H5 system for unifying login sessions between clients according to claim 5, wherein the unified session management center is further configured to receive a call request sent by any one of the clients, the call request includes a channel number of the client, return call session information to the client, and store the channel number of the client in the session storage object.
7. The H5 inter-client login session unification system of claim 5, wherein the system further comprises a generic server;
the universal server is used for receiving service requests sent by different clients, the service requests comprise client identifiers of corresponding clients, and the requested service data are returned to the corresponding clients according to the client identifiers.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910847279.XA CN110557396B (en) | 2019-09-09 | 2019-09-09 | Method and system for unifying login sessions between H5 clients |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910847279.XA CN110557396B (en) | 2019-09-09 | 2019-09-09 | Method and system for unifying login sessions between H5 clients |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110557396A CN110557396A (en) | 2019-12-10 |
| CN110557396B true CN110557396B (en) | 2022-03-15 |
Family
ID=68739669
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910847279.XA Active CN110557396B (en) | 2019-09-09 | 2019-09-09 | Method and system for unifying login sessions between H5 clients |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110557396B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114531471A (en) * | 2020-11-09 | 2022-05-24 | 航天信息股份有限公司 | Login state maintenance method, device, equipment and medium |
| CN114416195B (en) * | 2021-12-24 | 2023-08-18 | 青岛海尔科技有限公司 | H5 page loading method and device, intelligent terminal and server |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1914612A (en) * | 2004-03-04 | 2007-02-14 | 国际商业机器公司 | Timely update of a web page |
| CN101159925A (en) * | 2007-09-13 | 2008-04-09 | 中兴通讯股份有限公司 | Method of implementing detection mechanism of digital cluster dispatching desk |
| US8667575B2 (en) * | 2009-12-23 | 2014-03-04 | Citrix Systems, Inc. | Systems and methods for AAA-traffic management information sharing across cores in a multi-core system |
| US8806601B2 (en) * | 2008-02-29 | 2014-08-12 | International Business Machines Corporation | Non-interactive entity application proxy method and system |
| CN104410674A (en) * | 2014-11-12 | 2015-03-11 | 国云科技股份有限公司 | A WEB session synchronization method of a single sign on system |
| CN104580226A (en) * | 2015-01-15 | 2015-04-29 | 上海瀚之友信息技术服务有限公司 | Session data sharing system and method |
| CN105138395A (en) * | 2015-06-24 | 2015-12-09 | 江苏南亿迪纳数字科技发展有限公司 | Session management method |
| CN105245535A (en) * | 2015-10-23 | 2016-01-13 | 上海斐讯数据通信技术有限公司 | Multi-client uniform management method and system |
| CN106973062A (en) * | 2017-04-27 | 2017-07-21 | 努比亚技术有限公司 | A kind of conversation managing method and server |
| CN107395711A (en) * | 2017-07-17 | 2017-11-24 | 中国农业银行股份有限公司 | Heterogeneous system session access method and relevant apparatus |
| CN108509604A (en) * | 2018-03-30 | 2018-09-07 | 成都优易数据有限公司 | A kind of method of the data sharing duke groups of multiple Shipping Options Pages |
| CN108683675A (en) * | 2018-05-23 | 2018-10-19 | 南京联创信息科技有限公司 | Report activating method based on SSO extending sessions durations |
-
2019
- 2019-09-09 CN CN201910847279.XA patent/CN110557396B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1914612A (en) * | 2004-03-04 | 2007-02-14 | 国际商业机器公司 | Timely update of a web page |
| CN101159925A (en) * | 2007-09-13 | 2008-04-09 | 中兴通讯股份有限公司 | Method of implementing detection mechanism of digital cluster dispatching desk |
| US8806601B2 (en) * | 2008-02-29 | 2014-08-12 | International Business Machines Corporation | Non-interactive entity application proxy method and system |
| US8667575B2 (en) * | 2009-12-23 | 2014-03-04 | Citrix Systems, Inc. | Systems and methods for AAA-traffic management information sharing across cores in a multi-core system |
| CN104410674A (en) * | 2014-11-12 | 2015-03-11 | 国云科技股份有限公司 | A WEB session synchronization method of a single sign on system |
| CN104580226A (en) * | 2015-01-15 | 2015-04-29 | 上海瀚之友信息技术服务有限公司 | Session data sharing system and method |
| CN105138395A (en) * | 2015-06-24 | 2015-12-09 | 江苏南亿迪纳数字科技发展有限公司 | Session management method |
| CN105245535A (en) * | 2015-10-23 | 2016-01-13 | 上海斐讯数据通信技术有限公司 | Multi-client uniform management method and system |
| CN106973062A (en) * | 2017-04-27 | 2017-07-21 | 努比亚技术有限公司 | A kind of conversation managing method and server |
| CN107395711A (en) * | 2017-07-17 | 2017-11-24 | 中国农业银行股份有限公司 | Heterogeneous system session access method and relevant apparatus |
| CN108509604A (en) * | 2018-03-30 | 2018-09-07 | 成都优易数据有限公司 | A kind of method of the data sharing duke groups of multiple Shipping Options Pages |
| CN108683675A (en) * | 2018-05-23 | 2018-10-19 | 南京联创信息科技有限公司 | Report activating method based on SSO extending sessions durations |
Non-Patent Citations (2)
| Title |
|---|
| webview HttpClient怎么保持会话session统一;博客园;《https://www.cnblogs.com/itcqx/p/5777503.html》;20160816;全文 * |
| 多服务器下如何共享Session;史杨;《电脑知识与技术》;20150630;第11卷(第16期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110557396A (en) | 2019-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2741541B1 (en) | Capability inquiry method, communication terminal and application server | |
| CN110933180B (en) | Communication establishment method, device, load equipment and storage medium | |
| EP1958417B1 (en) | Message handling in an ip multimedia subsystem | |
| CN110557396B (en) | Method and system for unifying login sessions between H5 clients | |
| US9363660B2 (en) | Processing data in a cluster of network nodes | |
| US20120215894A1 (en) | Method, apparatus and system for selecting service | |
| US8874684B2 (en) | Facilitating subscription services in the IMS | |
| JP2017510116A (en) | Method and server for enabling a first user to automatically detect a second user's social network identifier and the respective status of this second user in those social networks | |
| US8966091B2 (en) | Method of distinguishing a plurality of UEs sharing one PUID and a device thereof | |
| EP1902570A1 (en) | System and method for providing registration-coupled subscriptions in a session initiation protocol (sip) environment | |
| CN101426261B (en) | Method for service handling of multimedia subsystem, P-CSCF, I-CSCF and subsystem | |
| US7949767B2 (en) | System and method for multiple address of record registration using a single explicit SIP request | |
| CN113329447A (en) | Communication method and system acting on IP multimedia subsystem IMS slice network | |
| WO2012000455A1 (en) | Client terminal and load balancing method | |
| CN112733051A (en) | Websocket-based information push management system and method | |
| EP2863603A1 (en) | A method for optimizing the capability discovery of terminals in an IMS network | |
| EP3402169B1 (en) | Data processing | |
| CN103581176A (en) | Session initiation protocol (SIP) information registering refreshing method and device | |
| GB2563251A (en) | Terminal device, data processing apparatuses and methods | |
| US20090037564A1 (en) | System and Method for Multiple Address of Record Deregistration Using a Single SIP Request | |
| US20140321280A1 (en) | Processing data | |
| US20200196267A1 (en) | A Method and Devices of Notifying a First User Equipment, UE, of a Subscriber in a Telecommunication Network on a Dialog Status of a Second UE of said same Subscriber | |
| EP4096183A1 (en) | Method for realizing communication sessions using a telecommunications network and involving at least one user equipment, telecommunications network, processing entity or functionality, user equipment, program and computer-readable medium | |
| GB2525441A (en) | Data Processing | |
| CN106255197B (en) | User access method of distributed soft switching system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: No.88, Huaihai Road, Qinhuai District, Nanjing, Jiangsu 210001 Patentee after: Nanyin Faba Consumer Finance Co.,Ltd. Address before: No.88, Huaihai Road, Qinhuai District, Nanjing, Jiangsu 210001 Patentee before: SUNING CONSUMER FINANCE Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |