14 results about "Fully qualified domain name" patented technology

Embodiments include methods for a network data analytics function (NWDAF) configured to assist with application detection in a communication network. Such methods include receiving, from a consumer network function (cNF) of the communication network, an analytic request related to assisted application detection and based on the analytic request, sending to a first DNS resolver associated with the communication network an exposure request for events related to fully qualified domain name (FQDN)-to-address mapping for application servers associated with applications. Such methods also include receiving from the first DNS resolver a first FQDN associated with a first application, in accordance with the exposure request, and based on the first FQDN, determining one or more packet flow descriptions (PFDs) associated with the first application. Such methods also include sending to the cNF an analytic result comprising the one or more PFDs, in accordance with the analytic request.

The application discloses a wireless communication method, a wireless communication platform, an electronic device and a computer readable storage medium, receiving first DNS configuration information associated with a first application network element sent by an edge computing server; the first DNS configuration information comprises at least one of a data network address, an application network element service identifier, a data network access identifier, a fully qualified domain name, a service filtering identifier and domain name system information; configuring the first DNS configuration information for a to-be-configured network element associated with the first application network element in a core network device, and sending DNS feedback information to the edge computing server; the DNS feedback information is used for indicating that the to-be-configured network element is successfully configured, or indicating that the to-be-configured network element fails to be configured. In this way, it is ensured that a terminal device can access services carried on the edge computing server through local DNS services.

Various aspects of the present disclosure relate to registration and authentication using multiple certificates. A network equipment (NE) may transmit a request for a vendor-signed certificate to a server device associated with a vendor of the NE and based on a security key and a fully qualified domain name (FQDN). The NE may receive the vendor-signed certificate from the server device associated with the vendor of the NE. The NE may transmit a request for an operator-signed certificate to a server device associated with an operator of the NE and based on the vendor-signed certificate. The NE may receive the operator-signed certificate from the server device associated with the operator of the NE. The NE may establish a secure connection between the NE and a core network (CN) based on the vendor-signed certificate and the operator-signed certificate.

An identifier, for example, an identifier of a domain and / or a host of the domain (e.g., a fully qualified domain name (FQDN), etc.), such as a service management device (e.g., a server, a web server, a computing device, a web host device, a webpage, etc.), may be modified (e.g., hashed, encrypted, etc.) by a network device (e.g., a server, a domain name system (DNS) server, a DNS over hypertext transfer protocol secure (HTTPS) server / gateway (DoH server), DNS over Transport Layer Security (TLS) server / gateway (DoT server), a network management device, a computing device, etc.), sent to a user device (e.g., a client device, a smart device, a mobile device, a content output device, a computing device, a web browser, a search engine, etc.), and reused by the user device to request a service (e.g., a web service, a webpage, a file, content, a content item, etc.).

A distributed unit (DU) includes a memory having non-transitory instructions stored therein and a processor coupled to the memory, and being configured to execute the instructions, thereby causing the DU to transmit a first power-on notification (PON) to an element management system (EMS), after transmitting the first PON, communicate with a first virtual centralized unit (vCU) using a stored first vCU fully qualified domain name (FQDN), and transmit a sequence of second PONs to the EMS in parallel with communicating with the vCU.

Responsive to domain name server (DNS) flood conditions being detected, a fully qualified domain name (FQDN) of each DNS query is checked against a table of legitimate FQDNs, and DNS queries having FQDNs that are verified as legitimate queries to pass to the DNS server are allowed, and DNS queries having FQDNs not verified as legitimate queries from passing to the DNS server are blocked.

The present disclosure provides a communication method, device, electronic equipment and storage medium, and relates to the technical field of wireless communication. The method comprises: a policy control function (PCF) network element receiving a target message sent by a target network element (NF), wherein the target message comprises any one or more of the following: a target Internet Protocol (IP) address; a target fully qualified domain name (FQDN); a data network name (DNN) of a target protocol data unit (PDU) session; and single network slice selection assistance information (S-NSSAI) of the target PDU session. The present disclosure transmits data through a user plane, collects data from a user equipment by a core network element through the user plane, and establishes a channel between the user equipment and the core network element to collect user data, thereby solving the problem of low data transmission efficiency through a control plane.

The application discloses a DNS query method, device, equipment and medium, and belongs to the communication technical field. The DNS query method comprises the following steps: a first communication device receives a DNS query and obtains a fully qualified domain name (FQDN); the first communication device sends first information to a second communication device; the first information comprises the FQDN or N server IP addresses corresponding to the FQDN; N is a positive integer; the first communication device obtains server experience information corresponding to the N server IP addresses from the second communication device; the server experience information is used for indicating the service experience of a server corresponding to each server IP address; and the first communication device sends a DNS response to a terminal based on the server experience information.

A mobility management function residing in a visited Public Land Mobile Network (vPLMN) receives, from a Network Repository Function (NRF) residing in a home Public Land Mobile Network (hPLMN), a network address and / or a fully qualified domain name (FQDN) of a home network function (hNF) residing in the hPLMN. The mobility management function creates a network service request, associated with a User Equipment device (UE) that is roaming in the vPLMN, where the network service request comprises the network address and / or the FQDN. The mobility management function sends the network service request to a visited network function (vNF) residing in the vPLMN, and receives, via the vNF, results of execution of a network service by the hNF, and uses the results for handling the roaming UE’s traffic in the vPLMN.

Techniques for wildcard based private application access are disclosed. In some embodiments, a system, a process, and / or a computer program product for wildcard based private application access includes receiving a request for access to an application over a secure access service edge (SASE) network for a user associated with an enterprise; determining if the request for access to the application matches a wildcard (e.g., the wildcard can be configured by an administrator of the enterprise for matching a fully qualified domain name (FQDN) for the application); and automatically configuring access information (e.g., IP address, protocol, and destination port) for the application that matches the wildcard.

An identifier, for example, an identifier of a domain and / or a host of the domain (e.g., a fully qualified domain name (FQDN), etc.), such as a service management device (e.g., a server, a web server, a computing device, a web host device, a webpage, etc.), may be modified (e.g., hashed, encrypted, etc.) by a network device (e.g., a server, a domain name system (DNS) server, a DNS over hypertext transfer protocol secure (HTTPS) server / gateway (DoH server), DNS over Transport Layer Security (TLS) server / gateway (DoT server), a network management device, a computing device, etc.), sent to a user device (e.g., a client device, a smart device, a mobile device, a content output device, a computing device, a web browser, a search engine, etc.), and reused by the user device to request a service (e.g., a web service, a webpage, a file, content, a content item, etc.).

Methods and apparatuses are described herein for providing fine-grained QoS rules within UE Policies. A network entity may receive triggers to update the policies of a user equipment (UE) with parameters based on input such as input from a third party. The network entity may derive fine-grained quality of service (QoS) rules and corresponding QoS Profiles and delivers them to the UE using a UE Policy container via the Non-Access Stratum (NAS). The fine-grained rules may comprise: a destination fully qualified domain name (FQDN) or uniform resource locator (URL), an Application ID, a User Route Selection Policy precedence value, etc. The fine-grained rules also provide mechanisms for time gating or volume gating. The UE may request new QoS treatment resulting in UE Policy update and may use the information in the fine-grained QoS rules when establishing or modifying PDU Session to apply QoS Flow Identifier (QFI) marking.

This disclosure describes systems, methods, and devices related to managing Internet Protocol Security (IPsec) for virtual private network (VPN) concentrators. A method may include: identifying, by an edge gateway backend system, a first IPsec tunnel, a second IPsec tunnel, and a third IPsec tunnel between a VPN client and a VPN concentrator of the edge gateway backend system; determining, by the edge gateway backend system, that the first IPsec tunnel is a highest priority tunnel between the VPN client and the VPN concentrator; determining, by the edge gateway backend system, that the highest priority tunnel between the VPN client and the VPN concentrator is active; and deactivating, by the edge gateway backend system, fully qualified domain names of the second IPsec tunnel and the third IPsec tunnel from the VPN concentrator based on the determination that the highest priority tunnel between the VPN client and the VPN concentrator is active.

A gateway router is provisioned with network access by a service provider computing system associated with a service provider. The service provider computing system generates a domain name service (DNS) profile for a user of the gateway router based on customer profile data associated with the user. The DNS profile includes a predicted fully qualified domain name (FQDN). During an initialization process, the gateway router receives the DNS profile from the service provider computing system and stores the DNS profile in a DNS cache. Subsequently, the gateway router obtains an internet protocol (IP) address corresponding to the predicted FQDN in the DNS profile and stores the IP address in the DNS cache. Subsequently, the gateway router implements a local area network (LAN) and establishes connection to one or more client computing devices.