CN112231120A - Service access method and device - Google Patents
Service access method and device Download PDFInfo
- Publication number
- CN112231120A CN112231120A CN202011113857.6A CN202011113857A CN112231120A CN 112231120 A CN112231120 A CN 112231120A CN 202011113857 A CN202011113857 A CN 202011113857A CN 112231120 A CN112231120 A CN 112231120A
- Authority
- CN
- China
- Prior art keywords
- service
- target
- target service
- white list
- name
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 23
- 241000412611 Consul Species 0.000 claims description 6
- 238000001514 detection method Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 claims description 4
- 239000007858 starting material Substances 0.000 claims description 4
- 230000007246 mechanism Effects 0.000 abstract description 9
- 238000013461 design Methods 0.000 abstract description 4
- 238000004891 communication Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a service access method and a device, which relate to the technical field of communication networks, wherein the method comprises the following steps: acquiring a service access request, wherein the service access request is used for requesting access to a target service; detecting whether the target service is a service in a service white list; if the target service is the service in the service white list, modifying a Pod network Interconnection Protocol (IP) of the target service into a service name, and calling the target service according to the service name; and if the target service is not the service in the service white list, calling the target service according to the Pod IP of the target service. The problem that the existing design cannot meet the requirements of a Service scene is solved, the architecture upgrading of an application level can be realized in a Service white list mode, the network call of the micro-Service simultaneously supports two mechanisms of Spring Cloud and Service Mesh, and the architecture upgrading is smooth and stable.
Description
Technical Field
The invention relates to a service access method and a service access device, and belongs to the technical field of communication networks.
Background
Under the existing Spring Cloud system, service call is that a client service acquires Pod information of a server service from Consul through a service name, and then the client service is directly connected to the Pod to perform network call. In the transition period from the Spring Cloud system to the Service Mesh, in order to ensure the stability of the Service, a small part of the Service is often upgraded first, a part of the Service is kept unchanged, and the upgraded Service is upgraded completely after being stabilized. However, the two existing sets of network calls can only operate independently in a self-mode, and cannot meet the requirements of a real service scene.
Disclosure of Invention
The invention aims to provide a service access method and a service access device, which are used for solving the problems in the prior art.
In order to achieve the purpose, the invention provides the following technical scheme:
according to a first aspect, an embodiment of the present invention provides a service access method, where the method includes:
acquiring a service access request, wherein the service access request is used for requesting access to a target service;
detecting whether the target service is a service in a service white list;
if the target service is the service in the service white list, modifying a Pod network Interconnection Protocol (IP) of the target service into a service name, and calling the target service according to the service name;
and if the target service is not the service in the service white list, calling the target service according to the PodIP of the target service.
Optionally, the invoking the target service according to the service name includes:
and forwarding the Service access request to the sidecar of the Service Mesh through an iptables routing strategy according to the Service name, and calling the target Service.
Optionally, the invoking the target service according to the service name includes:
intercepting the service access request accessed through the service name through the Envoy, and calling the target service through the Envoy.
Optionally, if the service is called by using a Feign calling method, the detecting whether the target service is a service in a service white list includes:
selecting a service instance from at least two service instances through a load balancing algorithm;
and detecting whether the target service is a service in a service white list or not through the selected service instance.
Optionally, the modifying the Pod internet protocol IP of the target service to a service name includes:
and if the target service is the service in the service white list, changing the PodIP in the Pod Server Info into the service name.
Optionally, if a service is called in a way of calling a gRPC, the detecting whether the target service is a service in a service white list includes:
when the gPC Starter creates a nettypeChannel through builder, detecting whether the target service is a service in a service white list.
Optionally, the modifying the Pod internet protocol IP of the target service to a service name, and calling the target service according to the service name includes:
and modifying PodIP of the target service into the service name, and executing the created netyChannel.
Optionally, the method further includes:
and after receiving the service access request, acquiring PodIP corresponding to the service name from Consul according to the service name of the target service.
In a second aspect, there is provided a service access apparatus, the apparatus comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a service access request which is used for requesting to access a target service;
the detection module is used for detecting whether the target service is a service in a service white list or not;
the calling module is used for modifying the Pod network interconnection protocol IP of the target service into a service name when the target service is the service in the service white list, and calling the target service according to the service name; and when the target service is not the service in the service white list, calling the target service according to the Pod IP of the target service.
The method comprises the steps of obtaining a service access request, wherein the service access request is used for requesting to access a target service; detecting whether the target service is a service in a service white list; if the target service is the service in the service white list, modifying a Pod network Interconnection Protocol (IP) of the target service into a service name, and calling the target service according to the service name; and if the target service is not the service in the service white list, calling the target service according to the Pod IP of the target service. The problem that the existing design cannot meet the requirements of a Service scene is solved, the architecture upgrading of an application level can be realized in a Service white list mode, the network call of the micro-Service simultaneously supports two mechanisms of Spring Cloud and Service Mesh, and the architecture upgrading is smooth and stable.
The foregoing description is only an overview of the technical solutions of the present invention, and in order to make the technical solutions of the present invention more clearly understood and to implement them in accordance with the contents of the description, the following detailed description is given with reference to the preferred embodiments of the present invention and the accompanying drawings.
Drawings
FIG. 1 is a flow chart of a method of providing service access according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a service access device according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
In addition, the technical features involved in the different embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
First, to facilitate understanding, a brief description will be given of terms that may be referred to in this application. Wherein:
spring Cloud is a micro service architecture commonly used by Java technology system.
Service Mesh: a service grid.
Feign: http calls middleware.
gRPC: the network invokes middleware.
Kubernetes: a containerization orchestration system.
Service: definition of a service in kubernets.
Pod: under the minimum definition of an instance under one Service in kubernets, one Service may have multiple Pod.
Referring to fig. 1, a flowchart of a method for accessing a service according to an embodiment of the present application is shown, where as shown in fig. 1, the method includes:
when the target service needs to be accessed, the client can send out a service access request for accessing the target service.
the service white list can be a default service list of the system or a self-defined list, and when the service white list is actually implemented, the content of the service white list can be updated according to requirements. In actual implementation, the Service in the Service white list may be a Service that has been upgraded to Service Mesh.
Optionally, there are two common service invoking manners, namely Feign and gRPC, under the Spring Cloud micro-service system, and based on the difference in invoking manners, the detection manner in this step is also different, so that, in one possible implementation manner, this step may include the following two possible implementation manners:
in a first possible implementation manner, if a Feign calling manner is used to call a service, the step includes:
firstly, selecting a service instance from at least two service instances through a load balancing algorithm;
when the service is called by using the calling mode of Feign, the IstioProperties receiving configured white List service can be added, and in order to maintain the retry mechanism and the fusing mechanism, after the Pod Server List in Consul is acquired by the Watch mechanism in the Feign Starter, a Server Info is selected by the load balancing algorithm.
Secondly, whether the target service is a service in a service white list is detected through the selected service instance.
After the Server Info is selected, it can be detected whether the target service is a service in the service white list.
In a second possible implementation manner, if the service is called by using the calling manner of the gRPC, the step includes:
when the adopted calling mode is the gPC, adding IstioProperties to receive the configured white list service, and detecting whether the target service is the service in the service white list or not when the gPC Starter creates a NettyChannel through the builder.
and when the target service is the service in the service white list, replacing the PodIP of the target service with the service name, and calling the target service according to the service name.
When the service calling mode used in step 102 is Feign, this step may be implemented by changing PodIP in the Pod Server Info to service name, and then forwarding the service access request and calling the target service.
When the calling mode used in step 102 is gRPC, this step may be implemented by directly changing PodIP to service name, and executing build.
After the PodIP is changed to the service name, the step of calling the target service includes: and forwarding the Service access request to the sidecar of the Service Mesh through an iptables routing strategy according to the Service name, and calling the target Service.
Optionally, the service access request accessed through the service name may be intercepted by the Envoy, and the target service may be invoked through the Envoy.
And 104, if the target service is not the service in the service white list, calling the target service according to the Pod IP of the target service.
And if the detection result is that the target service is not the service in the service white list, directly calling the target service according to the Pod IP.
In a possible embodiment of this embodiment, a service calling manner adopted is Feign for example, and when a server service is started, meta information of an instance, including IP and Port, is registered with a consul; when the client service calls the server service, an instance set corresponding to the server service can be found from the consul according to the service name of the called target service; then, selecting an instance from the instance information set according to a load balancing algorithm, detecting whether a target service is a service in a white list, if so, replacing the PodIP with a service name, at the moment, a service access request accessed through the service name is intercepted by the Envoy, and acquiring a service server2 corresponding to the PodIP through a service discovery mechanism of the Envoy, such as an XDS mechanism; and if the target service is not a white list service, the server1 is called directly through PodIP.
In summary, by obtaining a service access request, the service access request is used for requesting access to a target service; detecting whether the target service is a service in a service white list; if the target service is the service in the service white list, modifying a Pod network Interconnection Protocol (IP) of the target service into a service name, and calling the target service according to the service name; and if the target service is not the service in the service white list, calling the target service according to the Pod IP of the target service. The problem that the existing design cannot meet the requirements of a Service scene is solved, the architecture upgrading of an application level can be realized in a Service white list mode, the network call of the micro-Service simultaneously supports two mechanisms of Spring Cloud and Service Mesh, and the architecture upgrading is smooth and stable.
Referring to fig. 2, a schematic structural diagram of a service access device according to an embodiment of the present application is shown, and as shown in fig. 2, the service access device may include:
an obtaining module 310, configured to obtain a service access request, where the service access request is used to request access to a target service;
a detecting module 320, configured to detect whether the target service is a service in a service white list;
a calling module 330, configured to modify a Pod internet protocol IP of the target service to a service name when the target service is a service in the service white list, and call the target service according to the service name; and when the target service is not the service in the service white list, calling the target service according to the Pod IP of the target service.
In summary, by obtaining a service access request, the service access request is used for requesting access to a target service; detecting whether the target service is a service in a service white list; if the target service is the service in the service white list, modifying a Pod network Interconnection Protocol (IP) of the target service into a service name, and calling the target service according to the service name; and if the target service is not the service in the service white list, calling the target service according to the Pod IP of the target service. The problem that the existing design cannot meet the requirements of a Service scene is solved, the architecture upgrading of an application level can be realized in a Service white list mode, the network call of the micro-Service simultaneously supports two mechanisms of Spring Cloud and Service Mesh, and the architecture upgrading is smooth and stable.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (9)
1. A method for service access, the method comprising:
acquiring a service access request, wherein the service access request is used for requesting access to a target service;
detecting whether the target service is a service in a service white list;
if the target service is the service in the service white list, modifying a Pod network Interconnection Protocol (IP) of the target service into a service name, and calling the target service according to the service name;
and if the target service is not the service in the service white list, calling the target service according to the Pod IP of the target service.
2. The method of claim 1, wherein said invoking the target service according to the service name comprises:
and forwarding the Service access request to the sidecar of the Service Mesh through an iptables routing strategy according to the Service name, and calling the target Service.
3. The method of claim 1, wherein said invoking the target service according to the service name comprises:
intercepting the service access request accessed through the service name through the Envoy, and calling the target service through the Envoy.
4. The method of claim 1, wherein if the Feign call mode is used to call a service, the detecting whether the target service is a service in a service white list comprises:
selecting a service instance from at least two service instances through a load balancing algorithm;
and detecting whether the target service is a service in a service white list or not through the selected service instance.
5. The method of claim 4, wherein modifying the Pod Internet Protocol (IP) of the target service to a service name comprises:
and if the target service is the service in the service white list, changing the PodIP in the Pod ServerInfo into the service name.
6. The method of claim 1, wherein if a service is called by a gRPC, the detecting whether the target service is a service in a service white list comprises:
when the gPC Starter creates a nettypeChannel through builder, detecting whether the target service is a service in a service white list.
7. The method of claim 6, wherein the modifying the Pod Internet Protocol (IP) of the target service to a service name, and invoking the target service according to the service name comprises:
and modifying PodIP of the target service into the service name, and executing the created netyChannel.
8. The method of any of claims 1 to 7, further comprising:
and after receiving the service access request, acquiring PodIP corresponding to the service name from Consul according to the service name of the target service.
9. A service access apparatus, the apparatus comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a service access request which is used for requesting to access a target service;
the detection module is used for detecting whether the target service is a service in a service white list or not;
the calling module is used for modifying the Pod network interconnection protocol IP of the target service into a service name when the target service is the service in the service white list, and calling the target service according to the service name; and when the target service is not the service in the service white list, calling the target service according to the PodIP of the target service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011113857.6A CN112231120A (en) | 2020-10-17 | 2020-10-17 | Service access method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011113857.6A CN112231120A (en) | 2020-10-17 | 2020-10-17 | Service access method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112231120A true CN112231120A (en) | 2021-01-15 |
Family
ID=74117842
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011113857.6A Pending CN112231120A (en) | 2020-10-17 | 2020-10-17 | Service access method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112231120A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112311786A (en) * | 2020-10-28 | 2021-02-02 | 北京健康之家科技有限公司 | Service request processing method and device, storage medium and computing equipment |
| CN112988223A (en) * | 2021-03-25 | 2021-06-18 | 北京百度网讯科技有限公司 | Frame integration method and device, electronic equipment and storage medium |
| CN114125039A (en) * | 2021-12-08 | 2022-03-01 | 阿里云计算有限公司 | Discovery and control method and device for access relation between services |
| CN114650276A (en) * | 2022-02-24 | 2022-06-21 | 北京健康之家科技有限公司 | Service request processing method, electronic equipment terminal and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018107943A1 (en) * | 2016-12-13 | 2018-06-21 | 腾讯科技（深圳）有限公司 | Network access control method, apparatus and system |
| US20190028880A1 (en) * | 2016-03-25 | 2019-01-24 | Huawei Technologies Co., Ltd. | Method for accessing context data by network service component, apparatus, and system |
| CN110062043A (en) * | 2019-04-16 | 2019-07-26 | 杭州朗和科技有限公司 | Service administering method, service controlling device, storage medium and electronic equipment |
| CN110868465A (en) * | 2019-11-13 | 2020-03-06 | 北京浪潮数据技术有限公司 | Load balancing system and method for container cloud |
-
2020
- 2020-10-17 CN CN202011113857.6A patent/CN112231120A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190028880A1 (en) * | 2016-03-25 | 2019-01-24 | Huawei Technologies Co., Ltd. | Method for accessing context data by network service component, apparatus, and system |
| WO2018107943A1 (en) * | 2016-12-13 | 2018-06-21 | 腾讯科技（深圳）有限公司 | Network access control method, apparatus and system |
| CN110062043A (en) * | 2019-04-16 | 2019-07-26 | 杭州朗和科技有限公司 | Service administering method, service controlling device, storage medium and electronic equipment |
| CN110868465A (en) * | 2019-11-13 | 2020-03-06 | 北京浪潮数据技术有限公司 | Load balancing system and method for container cloud |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112311786A (en) * | 2020-10-28 | 2021-02-02 | 北京健康之家科技有限公司 | Service request processing method and device, storage medium and computing equipment |
| CN112311786B (en) * | 2020-10-28 | 2023-06-13 | 北京水滴科技集团有限公司 | Service request processing method and device, storage medium and computing equipment |
| CN112988223A (en) * | 2021-03-25 | 2021-06-18 | 北京百度网讯科技有限公司 | Frame integration method and device, electronic equipment and storage medium |
| CN112988223B (en) * | 2021-03-25 | 2023-08-04 | 北京百度网讯科技有限公司 | Frame integration method, frame integration device, electronic equipment and storage medium |
| CN114125039A (en) * | 2021-12-08 | 2022-03-01 | 阿里云计算有限公司 | Discovery and control method and device for access relation between services |
| CN114650276A (en) * | 2022-02-24 | 2022-06-21 | 北京健康之家科技有限公司 | Service request processing method, electronic equipment terminal and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112231120A (en) | Service access method and device | |
| US10659952B2 (en) | Network slice selection policy updating method and apparatus | |
| CN109618005B (en) | Method for calling server and proxy server | |
| CN110990047B (en) | Fusion method and device for multiple microservice architectures | |
| CN109391592B (en) | Method and equipment for discovering network function service | |
| US10708376B2 (en) | Message bus service directory | |
| US8453158B2 (en) | Method, apparatus, and system for enhancing application reliability of a script-based service | |
| WO2013121362A2 (en) | M2m service enablement over access networks | |
| CN112311786B (en) | Service request processing method and device, storage medium and computing equipment | |
| CN106210049B (en) | Cluster communication method and system based on message queue | |
| US20130173734A1 (en) | Method and system for managing social notifications for mobile devices | |
| US11888957B2 (en) | Methods, systems, and computer readable media for locality and serving scope set based network function (NF) profile prioritization and message routing | |
| CN111884844A (en) | Message service access method and device based on zookeeper | |
| CN112732456A (en) | Micro-service calling method and device, electronic equipment and storage medium | |
| US7602762B1 (en) | System and method for determining when a CSCF should act like I-CSCF or like S-CSCF | |
| CN114930913A (en) | Method and apparatus for selecting user plane function | |
| EP2863603A1 (en) | A method for optimizing the capability discovery of terminals in an IMS network | |
| CN114466447B (en) | Cloud management end management system based on WiFi6 router | |
| CN114070734B (en) | Cloud platform adaptation frame, method, equipment and storage medium | |
| CN116319963A (en) | Service management method, system, terminal equipment and storage medium | |
| KR20200068101A (en) | Apparatus and method for detecting abnormal IoT terminal | |
| CN113422725A (en) | Routing strategy management method, system, equipment and medium for application program | |
| US10966144B2 (en) | Method and device for managing the connection of a terminal to an access network | |
| US20230292274A1 (en) | Methods, systems, and computer readable media for discovering network function service producers in a hierarchical network | |
| US20230345223A1 (en) | Methods, systems, and computer readable media for identifying roaming messages |
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 |