WO2017166252A1 - 服务节点选择、查询方法,装置及*** - Google Patents
服务节点选择、查询方法,装置及*** Download PDFInfo
- Publication number
- WO2017166252A1 WO2017166252A1 PCT/CN2016/078220 CN2016078220W WO2017166252A1 WO 2017166252 A1 WO2017166252 A1 WO 2017166252A1 CN 2016078220 W CN2016078220 W CN 2016078220W WO 2017166252 A1 WO2017166252 A1 WO 2017166252A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service node
- usage type
- type
- service
- information
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4541—Directories for service discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- 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/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
Definitions
- the present invention relates to communication technologies, and in particular, to a service node selection and query method, device and system.
- the control plane service node of the core network such as a Serving GPRS Support Node (SGSN) in a Universal Mobile Telecommunications System (UMTS) network, or The Mobility Management Entity (MME) in the Evolved Packet Core (EPC) network needs to support different types of user equipment.
- SGSN Serving GPRS Support Node
- UMTS Universal Mobile Telecommunications System
- MME Mobility Management Entity
- the control plane service node of the core network needs to select a correct user plane service node for the user equipment according to different types of user equipment, the user plane service node.
- the user plane service node For example, the Gateway GPRS Support Node (GGSN) in the UMTS network, or the Service-Gateway (S-GW)/PDN Gateway (Public Data Network-Gateway, P-GW for short) in the EPC network. ), or, when a user equipment selects the wrong control plane service node, select the correct control plane service node for the user equipment.
- GGSN Gateway GPRS Support Node
- S-GW Service-Gateway
- P-GW Public Data Network-Gateway
- the control plane serving node of the core network selects a user plane service node or another control plane service node for different user equipment according to the usage type of the user equipment. Specifically, the control plane service node of the core network queries the user domain service node or the control plane service node that meets the usage type in the corresponding Domain Name System (DNS) according to the acquired usage type of the user equipment.
- DNS Domain Name System
- the user plane service node or the control plane service node selected by the prior art often fails to meet the actual service requirements of the user equipment, thereby causing service failure.
- the embodiment of the invention provides a service node selection and query method, device and system, which are used to meet the actual service requirements of the user equipment.
- a first aspect of the embodiments of the present invention provides a service node selection method, including:
- the service node selected in this way is a service node that supports the private network type of the UE and can satisfy the service requested by the UE this time, and thus can ensure the service success of the UE.
- the method for obtaining the usage type of the UE according to the request message and selecting the auxiliary information is:
- the above method for acquiring the usage type of the UE according to the request message and selecting the auxiliary information is:
- the above method for acquiring the usage type of the UE according to the request message and selecting the auxiliary information is:
- the embodiments of the present invention provide the foregoing multiple methods to obtain the usage type and the selection assistance information, so that the control plane entity can flexibly select the acquisition mode according to actual conditions to improve the acquisition efficiency.
- one method for determining the service node to be selected based on the type of use and the selection of assistance information is:
- a service node to be selected is determined by DNS according to the usage type and the selection assistance information.
- the method can be specifically:
- the query response message includes a service node identifier of the service node served by the UE according to the usage type and the selected auxiliary information query.
- the above alternative method of determining the desired selected service node based on usage type and selection assistance information is:
- the specific process for obtaining at least one service node identifier and the corresponding relationship between the service node identifier and the selected auxiliary information by using the DNS in the method may be:
- the query response message includes a service node identifier of the at least one service node obtained by the DNS according to the usage type query, and a correspondence between the service node identifier and the selection assistance information.
- the above alternative method of determining the desired selected service node based on usage type and selection assistance information is:
- the network topology information includes a cell identifier and/or service node topology information of the UE.
- a second aspect of the present invention provides a service node query method, including:
- the service node query message includes a usage type of the UE and selection auxiliary information, where the selection auxiliary information includes at least one of a private network type and service attribute information; and further, according to the receiving Obtaining the service node identifier of the service node serving the UE, and then sending a query response message to the control plane entity, where the query response message includes the service node identifier of the service node serving the UE.
- the obtaining, according to the usage type and the selecting auxiliary information, the service node identifier of the service node that is required to be selected includes:
- mapping table Determining, in the preset mapping table, a service node identifier of the service node corresponding to the usage type and the selection assistance information according to the usage type and the selection assistance information, where the mapping table is used to record the usage type And selecting the auxiliary information and the correspondence relationship of the service node identifier.
- a third aspect of the present invention provides a control plane entity, including:
- a receiving module configured to receive a request message sent by the user equipment UE
- a processing module configured to acquire, according to the request message, a usage type of the UE, and select auxiliary information, where the selection assistance information includes at least one of a private network type and service attribute information;
- the processing module is specifically configured to:
- the processing module is further used to:
- the processing module is further used to:
- the processing module is further used to:
- the service node to be selected is determined by the domain name system DNS according to the usage type and the selection assistance information.
- the processing module includes:
- a first sending unit configured to send a service node query message to the DNS, where the service node query message includes the usage type and the selection auxiliary information;
- a first receiving unit configured to receive a query response message sent by the DNS, where the query response message includes a service node of a service node that is served by the UE according to the usage type and the selected auxiliary information query.
- the processing module is further used to:
- the processing module further includes:
- a second sending unit configured to send a service node query message to the DNS, where the service node query message includes the usage type
- a second receiving unit configured to receive the query response message sent by the DNS, where the query response message includes a service node identifier of the at least one service node obtained by the DNS according to the usage type query, and the service node identifier and Select the correspondence of the auxiliary information.
- the processing module is further used to:
- the network topology information includes a cell identifier and/or service node topology information of the UE.
- the service attribute information includes an access point name APN that the UE needs to access, a service request type of the UE, an application server domain name that the UE needs to access, and the UE needs to access. At least one of the application server IP addresses.
- the request message is specifically an Attach message, a TAU message, or a PDN setup message.
- a fourth aspect of the present invention provides a domain name system, including:
- a receiving module configured to receive a service node query message sent by the control plane entity, where the service node query message includes a usage type of the user equipment UE and selection auxiliary information, where the selection assistance information includes the private network type and the service attribute information.
- a processing module configured to acquire, according to the usage type and the selecting auxiliary information, a service node identifier of a service node serving the UE;
- a sending module configured to send a query response message to the control plane entity, where the query response message includes a service node identifier of a serving node serving the UE.
- the processing module is specifically configured to:
- mapping table Determining, in the preset mapping table, a service node identifier of the service node corresponding to the usage type and the selection assistance information according to the usage type and the selection assistance information, where the mapping table is used to record the usage type And selecting the auxiliary information and the correspondence relationship of the service node identifier.
- a fifth aspect of the present invention provides a control plane entity, including a memory and a processor
- the memory is used to store program instructions, and the processor is used to call program instructions in the memory to perform the following methods:
- the selection assistance information includes at least one of a private network type and service attribute information
- the processor is also used to:
- the usage type is obtained from the request message, and the private network type is obtained according to the correspondence between the preset usage type and the private network type and the usage type.
- the processor is also used to:
- the usage type and the service attribute information are obtained from the subscription data of the UE.
- the processor is also used to:
- the usage type is obtained by the context of the UE, and the service attribute information is obtained from the subscription data of the UE.
- the processor is also used to:
- a service node to be selected is determined by DNS according to the usage type and the selection assistance information.
- the processor is also used to:
- a service node query message is sent to the DNS, and the service node query message includes a usage type and selection auxiliary information.
- the query response message includes a service node identifier of the service node serving the UE obtained by the DNS according to the usage type and the selected auxiliary information query.
- the processor is also used to:
- the processor is also used to:
- a service node query message is sent to the DNS, and the service node query message includes a usage type.
- the query response message includes a service node identifier of the at least one service node obtained by the DNS according to the usage type query, and a correspondence between the service node identifier and the selected auxiliary information.
- the processor is also used to:
- the foregoing network topology information includes a cell identifier of the UE and/or service node topology information.
- the service attribute information includes an access point name APN that the UE needs to access, a service request type of the UE, an application server domain name that the UE needs to access, and an application server that the UE needs to access. At least one of the IP addresses.
- the request message is specifically an Attach message, a TAU message, or a PDN setup message.
- a sixth aspect of the present invention provides a domain name system including a memory and a processor
- the memory is used to store program instructions, and the processor is used to call program instructions in the memory to perform the following methods:
- the service node query message includes a usage type of the UE and selection auxiliary information
- the selection assistance information includes at least one of a private network type and service attribute information
- the service node identifier of the service node serving the UE is obtained according to the usage type and the selection assistance information.
- the control plane entity Sending a query response message to the control plane entity, where the query response message includes a service node identifier of the serving node serving the UE.
- the processor is specifically used to:
- the service node serving the UE can be selected based on the usage type and the selection assistance information, thereby ensuring the service success of the UE.
- FIG. 1 is a schematic structural diagram of a method for selecting a service node according to the present invention
- Embodiment 1 is a schematic flowchart of Embodiment 1 of a method for selecting a service node according to the present invention
- Embodiment 3 is a schematic flowchart of Embodiment 2 of a method for selecting a service node according to the present invention
- Embodiment 4 is a schematic flowchart of Embodiment 3 of a method for selecting a service node according to the present invention
- FIG. 5 is a flowchart of an example of a service node selection method provided by the present invention.
- FIG. 6 is a block diagram of a first embodiment of a control plane entity according to an embodiment of the present disclosure
- FIG. 7 is a block diagram of a second embodiment of a control plane entity according to an embodiment of the present disclosure.
- FIG. 8 is a block diagram of a third embodiment of a control plane entity according to an embodiment of the present disclosure.
- FIG. 9 is a block diagram of a fourth embodiment of a control plane entity according to an embodiment of the present disclosure.
- FIG. 10 is a block diagram of a first embodiment of a domain name system according to an embodiment of the present disclosure.
- FIG. 11 is a block diagram of a second embodiment of a domain name system according to an embodiment of the present disclosure.
- a control plane serving node of the core network eg, an SGSN in a UMTS network, or an MME in an EPC network
- a user plane serving node eg, UMTS
- the S-GW/P-GW must also be able to support multiple different types of UEs.
- the control plane serving node since the UE may access the wrong control plane serving node when accessing the network (that is, the serving node accessed by the UE cannot serve the UE), then this control The polygon service node needs to select the correct control plane serving node for the UE and redirect the UE to the correct control plane serving node (which can serve the UE).
- the user plane service node may not be physically or logically unified due to different requirements of the service level agreement (SLA) for various services. For example, the user service such as web browsing has low requirements on time delay and rate.
- SLA service level agreement
- the deployment location of the user plane service node is close to the core network side, so as to avoid frequent switching of the user plane service node when the user moves.
- user services such as ultra-low latency communication are sensitive to delay.
- the deployment location of the user plane service node must be closer to the UE side to ensure the delay requirement of the service. Therefore, there are multiple user plane service nodes of different types and different deployment locations in the core network, and the user plane service nodes need to be selected according to the specific service requirements of the UE.
- the present invention proposes a method of selecting an optimal service node capable of serving a UE based on the above requirements.
- control plane service node and the user plane service node referred to in the present invention are:
- Control plane service node refers to the network element that provides control plane services in the 3GPP communication system.
- the same control plane service node can simultaneously configure UEs supporting multiple different types or different services, and provide corresponding services for these UEs, for example, mobile management services, security services, bearer management services, and the like customized according to user types.
- the MME is a control plane service node in a 4G architecture
- the SGSN is a control plane service node in a 3G architecture. It should be noted that if there is a dedicated network or network slice under the 5G architecture, the 5G private network or the control plane service node in the network slice should also be within the protection scope of the present invention.
- User plane service node refers to a network element that provides user plane services in the 3GPP communication system. There are a plurality of user plane service nodes of different types and different deployment locations in the network, and each user plane service node can provide services for a certain type of application scenario or user requirement. It should be noted that the S-GW, the PDN-GW, and the network entity or function that provides the user plane service for the UE in the 5G network, including but not limited to the 4G network. For example, the S-GW and the P-GW in the current EPC network can be considered as the user plane service node of the MBB service. In 5G, there may be new network entities or functions in the network as user plane service nodes to provide other new services, such as ultra-low latency communication services. The user plane service node referred to by the invention.
- FIG. 1 is a schematic structural diagram of a method for selecting a service node according to the present invention.
- the application scenario or user requirement provides services, and the UE selects a user plane service node that can serve itself through the control plane service node.
- FIG. 2 is a schematic flowchart of Embodiment 1 of a method for selecting a service node according to the present invention.
- an execution entity of the method is a control plane entity.
- the control plane entity may be a control plane serving node that actually serves the UE, or may be a control plane node that receives the UE request, such as an MME, an SGSN, or an entity that performs a control plane function in a 5G network.
- the method includes:
- the request message sent by the UE may be an Attach message, a TAU message, or a PDN setup message or other message related to establishing a bearer on the user plane. That is, as long as it is a message that can trigger the control plane entity to perform service node selection, it can be called a request message of the UE.
- the Attach message is an attach message
- the TAU message is a tracking area update message
- the PDN setup message is a PDN Connectivity Req message.
- S102 Acquire a usage type of the UE and select auxiliary information according to the foregoing request message, where the selection assistance information includes at least one of a private network type and service attribute information.
- the usage type is Usage Type.
- the private network type is a type of dedicated core network allocated by the UE to the UE according to the specific type and capability of the UE and/or the local policy of the network and the specific deployment manner after the UE subscribes or registers with the network.
- the private network type is DCN Type.
- the service attribute information corresponds to the service/service requested by the UE, and is used to specify the service/service that the UE desires to acquire this request.
- the service attribute information includes, but is not limited to, an access point name (APN) that the UE needs to access, a service request type of the UE, a service server domain name that the UE needs to access, and an application server IP address that the UE needs to access.
- API access point name
- the UE's usage type and the private network type are attributes of the UE itself, and cannot identify the specific service request of the UE, and the service attribute information of the UE may identify the specific service request of the UE.
- the usage type of one UE may be an MBB type
- the private network type may be an MBB DCN type.
- the UE can have multiple service requirements, such as voice communication, short message communication, ultra-reliable communication, ultra-low latency communication, etc., and these service requirements are described using service attributes.
- the above service node can be either a control plane service node or a user plane service node. That is, the control plane entity selects a control plane service node or a user plane service node serving the UE according to the actual needs of the UE.
- the current control plane entity after determining the serving node serving the UE, if the current control plane entity selects another control plane entity, that is, the current control plane entity cannot serve the UE, the current control plane entity initiates a redirection process, and The UE is redirected to a control plane entity capable of serving the UE. For example, the identifier of another control plane entity is sent to the access network node, and the access network node redirects the UE according to the identifier.
- the current control plane entity selects the user plane service node, the current control plane entity sends a session establishment request or a bearer setup request to the selected user plane serving node to establish a user plane bearer for the UE.
- the control plane entity selects a serving node serving the UE according to the usage type of the UE and selecting the auxiliary information, that is, according to the usage type, and also selects according to the private network type and/or service attribute information of the UE.
- the service node is configured such that the selected service node is a private network type that supports the UE, and can satisfy the service node of the requested service of the UE this time, thereby ensuring the service success of the UE.
- the specific manner of acquiring the usage type of the UE and selecting the auxiliary information according to the request message of the UE in the foregoing step S102 is as follows:
- the usage type may be directly obtained from the above request message, that is, the usage type may be directly carried in the request message; or the usage type may be obtained by querying the subscription data of the UE; or the usage type may also be obtained through the context of the UE.
- the method of obtaining the usage type by querying the subscription data of the UE reference may be made to the prior art, and details are not described herein again.
- the private network type can be directly obtained from the above request message, that is, the request message directly carries the private network type; or the private network type can be obtained according to the correspondence between the preset usage type and the private network type and the usage type. .
- the service attribute information may be obtained from the request message, that is, the service attribute information may be directly carried in the request message; or the service attribute information may be obtained by querying the subscription data of the UE.
- the method for obtaining the usage type and selecting the auxiliary information in the foregoing step S102 may specifically include:
- auxiliary information is only a private network type, it can be obtained by at least one of the following methods:
- the subscription data of the UE may be obtained from the Home Subscriber Server (HSS) through the location update process by the control plane entity.
- the control plane entity includes the identifier of the UE in the sent location update request message, and the HSS returns a location update response message to the control plane entity, where the subscription data corresponding to the identifier of the UE is included.
- control plane entity sends an acquisition context request to the control plane entity of the previous serving UE, where the UE includes the UE ID, and the original control plane entity returns an acquisition context response message, where the UE context is included, and the UE context includes the UE usage type.
- the control plane entity then obtains the usage type of the UE from the UE context.
- the usage type is obtained through the context of the UE, and the private network type is obtained according to the correspondence between the preset usage type and the private network type and the usage type.
- auxiliary information is only the business attribute information, it can be obtained by at least one of the following methods:
- the obtaining manner of the foregoing step S102 is a further combination based on the various methods in the above 1 and 2, and details are not described herein, but as long as it can be from the above 1 and Combinations derived by the respective methods in 2 are within the scope of protection of the present invention.
- the present embodiment relates to a process of determining a service node to be selected according to the type of use and the selection of auxiliary information.
- the service node to be selected is determined by DNS according to the type of use and the selection of the auxiliary information.
- FIG. 3 is a schematic flowchart of Embodiment 2 of a method for selecting a service node according to the present invention. As shown in FIG. 3, the specific process of determining a service node to be selected by using the DNS is as follows:
- the control plane entity sends a service node query message to the domain name system DNS.
- the service node query message includes the above usage type and selection auxiliary information.
- the DNS receives a service node query message sent by the control plane entity.
- the service node query message includes a usage type of the UE and selection auxiliary information, where the selection assistance information includes at least one of a private network type and service attribute information.
- the DNS acquires a service node identifier of the service node serving the UE according to the usage type and the selection auxiliary information.
- the DNS sends a query response message to the control plane entity.
- the query response message includes a service node identifier of a serving node serving the UE.
- the control plane entity receives the query response message sent by the DNS.
- the query response message includes a service node identifier of the service node serving the UE obtained by the DNS according to the usage type and the selected auxiliary information query.
- the information is sent to the DNS, and the correspondence between the different usage types and the selection auxiliary information and the service node is stored in the DNS, and the DNS queries according to the information.
- the selected service node identifier that is selected for the UE is returned. Thereby achieving accurate selection of the service node.
- step S203 specifically includes:
- the service node identifier of the service node corresponding to the usage type and the selection auxiliary information in the preset mapping table, where the mapping table is used for recording the usage type and selecting Select the correspondence between the auxiliary information and the service node identifier.
- the present embodiment relates to another method of determining a service node to be selected according to the type of use and the selection of auxiliary information.
- FIG. 4 is a schematic flowchart of Embodiment 3 of a method for selecting a service node according to the present invention.
- the specific process of obtaining at least one service node identifier and a correspondence between a service node identifier and a selection assistance information by using the DNS is as follows:
- the control plane entity sends a service node query message to the DNS, where the service node query message includes a usage type.
- the DNS receives a service node query message sent by the control plane entity.
- the service node query message includes the usage type of the UE.
- the DNS acquires a service node identifier of the at least one service node according to the usage type.
- the DNS sends a query response message to the control plane entity.
- the query response message includes a service node identifier of the at least one service node and a correspondence between the service node identifier and the selection assistance information.
- the control plane entity receives the query response message sent by the DNS.
- the query response message includes a service node identifier of the at least one service node obtained by the DNS according to the usage type query, and a correspondence between the service node identifier and the selection assistance information.
- the control plane entity determines, according to the selection assistance information and the correspondence between the service node identifier and the selection assistance information, the service node identifier of the service node served by the UE from the service node identifier of the at least one service node.
- control plane serving node only sends the usage type to the DNS, and further determines the serving node serving the UE according to the query result of the DNS and the selected auxiliary information.
- the DNS side does not need to make any changes, and the service node serving the UE is selected by the control plane serving node itself, thereby reducing network element variation and improving execution efficiency.
- the available selection is determined. Based on the selected service node, the control plane entity can further select a better service node in combination with the current network topology.
- the service node closest to the UE is determined from the above-mentioned available service nodes according to the network topology information.
- the access network node may report the message to the control plane entity when forwarding the UE request message. If the network topology information is service node topology information, it can be pre-configured in the control plane entity.
- the foregoing network topology information includes a cell identifier of the UE and/or user plane service node topology information.
- the service node identifier if the service node identifier is queried through the DNS, the usage type, the selection auxiliary information, and the network topology information may be uniformly sent to the DNS, and the DNS may uniformly query.
- the invention is not limited thereto.
- FIG. 5 is a flowchart of an example of a method for selecting a service node according to the present invention.
- FIG. 5 is an example of a control plane serving node, and the auxiliary information is only a private network type, and the private network type is carried in the request message as an example.
- the process of service node selection is:
- the UE sends a request message to the control plane serving node, where the request message includes a private network type.
- the UE's request message also includes the identity of the UE.
- the control plane serving node acquires a usage type of the UE from the subscription data of the UE.
- the subscription data of the UE may be obtained from a Home Subscriber Server (HSS) through a location update update location procedure.
- HSS Home Subscriber Server
- the control plane serving node includes the acquired identifier of the UE in the sent location update request message, and the HSS returns a location update response message to the control plane serving node, where the subscription data corresponding to the identifier of the UE is included.
- the control plane serving node obtains the usage type of the UE from the subscription data of the UE according to the identifier of the UE.
- the control plane serving node sends a service node query message to the DNS.
- the service node query message includes the usage type and the private network type.
- the DNS obtains a service node identifier of the service node serving the UE according to the usage type and the private network type.
- the DNS sends a query response message to the control plane service node.
- the query response message includes a service node identifier of a serving node serving the UE.
- the control plane serving node may establish a user plane bearer for the UE.
- FIG. 6 is a block diagram of a first embodiment of a control plane entity according to an embodiment of the present invention. As shown in FIG. 6, the control plane entity includes:
- the receiving module 601 is configured to receive a request message sent by the UE.
- the processing module 602 is configured to acquire, according to the request message, a usage type of the UE, and select auxiliary information, where the selection assistance information includes at least one of a private network type and service attribute information;
- a service node serving the UE is determined according to the type of use and the selection of the auxiliary information.
- control plane entity is used to implement the foregoing method embodiments, and the implementation principles and technical effects are similar, and details are not described herein again.
- processing module 602 is specifically configured to:
- the usage type is obtained from the request message, and the private network type is obtained according to the correspondence between the preset usage type and the private network type and the usage type.
- processing module 602 is further configured to:
- the usage type and the service attribute information are obtained from the subscription data of the UE.
- processing module 602 is further configured to:
- the usage type is obtained by the context of the UE, and the service attribute information is obtained from the subscription data of the UE.
- processing module 602 is further configured to:
- a service node to be selected is determined by DNS according to the usage type and the selection assistance information.
- FIG. 7 is a block diagram of a second embodiment of a control plane entity according to an embodiment of the present invention. As shown in FIG. 7, the processing module 602 includes:
- the first sending unit 6021 is configured to send a service node query message to the DNS, where the service node query message includes a usage type and selection auxiliary information.
- the first receiving unit 6022 is configured to receive a query response message sent by the DNS, where the query response message includes a service node identifier of the service node served by the UE according to the usage type and the selected auxiliary information query.
- processing module 602 is further configured to:
- FIG. 8 is a block diagram of a third embodiment of a control plane entity according to an embodiment of the present invention. As shown in FIG. 8, on the basis of FIG. 7, the processing module 602 further includes:
- the second sending unit 6023 is configured to send a service node query message to the DNS, where the service node query message includes a usage type.
- the second receiving unit 6024 is configured to receive a query response message sent by the DNS, where the query response message includes a service node identifier of the at least one service node obtained by the DNS according to the usage type query, and a correspondence between the service node identifier and the selected auxiliary information.
- processing module 602 is further configured to:
- the foregoing network topology information includes a cell identifier of the UE and/or service node topology information.
- the service attribute information includes at least one of an access point name APN that the UE needs to access, a service request type of the UE, an application server domain name that the UE needs to access, and an application server IP address that the UE needs to access.
- the request message is specifically an Attach message, a TAU message, or a PDN setup message.
- FIG. 9 is a block diagram of a fourth embodiment of a control plane entity according to an embodiment of the present invention, as shown in FIG. 9.
- the control plane entity includes a memory 701 and a processor 702.
- the memory 701 is used to store program instructions, and the processor 702 is configured to call program instructions in the memory 701 to perform the following methods:
- the selection assistance information includes at least one of a private network type and service attribute information
- processor 702 is further configured to:
- the usage type is obtained from the request message, and the private network type is obtained according to the correspondence between the preset usage type and the private network type and the usage type.
- processor 702 is further configured to:
- the usage type and the service attribute information are obtained from the subscription data of the UE.
- processor 702 is further configured to:
- the usage type is obtained by the context of the UE, and the service attribute information is obtained from the subscription data of the UE.
- processor 702 is further configured to:
- a service node to be selected is determined by DNS according to the usage type and the selection assistance information.
- processor 702 is further configured to:
- a service node query message is sent to the DNS, and the service node query message includes a usage type and selection auxiliary information.
- the query response message includes a service node identifier of the service node serving the UE obtained by the DNS according to the usage type and the selected auxiliary information query.
- processor 702 is further configured to:
- processor 702 is further configured to:
- a service node query message is sent to the DNS, and the service node query message includes a usage type.
- the query response message includes a service node identifier of the at least one service node obtained by the DNS according to the usage type query, and a correspondence between the service node identifier and the selected auxiliary information.
- processor 702 is further configured to:
- the foregoing network topology information includes a cell identifier of the UE and/or service node topology information.
- the service attribute information includes an access point name APN that the UE needs to access, a service request type of the UE, an application server domain name that the UE needs to access, and an application server IP address that the UE needs to access. At least one of them.
- the request message is specifically an Attach message, a TAU message, or a PDN setup message.
- FIG. 10 is a block diagram of a first embodiment of a domain name system according to an embodiment of the present invention. As shown in FIG. 10, the domain name system includes:
- the receiving module 801 is configured to receive a service node query message sent by the control plane entity, where the service node query message includes a usage type of the UE and selection auxiliary information, where the selection assistance information includes at least one of a private network type and service attribute information. .
- the processing module 802 is configured to obtain a service node identifier of the serving node serving the UE according to the usage type and the selection assistance information.
- the sending module 803 is configured to send a query response message to the control plane entity, where the query response message includes a service node identifier of the serving node serving the UE.
- processing module 802 is specifically configured to:
- FIG. 11 is a block diagram of a second embodiment of a domain name system according to an embodiment of the present invention. As shown in FIG. 11, the domain name system includes a memory 901 and a processor 902.
- the memory 901 is used to store program instructions, and the processor 902 is configured to call program instructions in the memory 901 to perform the following methods:
- the service node query message includes a usage type of the UE and selection auxiliary information
- the selection assistance information includes at least one of a private network type and service attribute information
- the service node identifier of the service node serving the UE is obtained according to the usage type and the selection assistance information.
- the control plane entity Sending a query response message to the control plane entity, where the query response message includes a service node identifier of the serving node serving the UE.
- processor 902 is specifically configured to:
- the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
- the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明实施例提供一种服务节点选择、查询方法,装置及***,该方法包括:接收UE发送的请求消息,并根据该请求消息获取UE的使用类型以及选择辅助信息,其中,选择辅助信息包括专网类型和业务属性信息中的至少一种;进而,根据所获得的使用类型和选择辅助信息来确定为UE服务的服务节点。通过这种方式所选择到的服务节点是支持UE的专网类型并且能够满足UE本次所请求的业务的服务节点,因此能够保证UE的业务成功。
Description
本发明涉及通信技术,尤其涉及一种服务节点选择、查询方法,装置及***。
随着移动通信网络的不断演进以及大量新应用的不断出现,不同的用户在不同的应用领域中逐渐形成了不同的通信特征,从而产生了不同的移动通信类型,比如:机器类通信,移动虚拟网络通信,公共安全通信等。这些不同的通信类型对应不同的用户设备类型。从核心网侧来看,不同的用户设备类型具有不同的通信需求,例如可用性需求、拥塞管理需求等。为满足不同类型的用户设备的需求,核心网的控制面服务节点,例如通用移动通信***(Universal Mobile Telecommunications System,简称UMTS)网络中的服务GPRS支持节点(Serving GPRS Support Node,简称SGSN),或核心分组网演进(Evolved Packet Core,简称EPC)网络中的移动性管理实体(Mobility Management Entity,简称MME)就需要支持不同类型的用户设备。例如,当某个用户设备需要接入网络以请求某种业务时,核心网的控制面服务节点需要根据用户设备的不同类型来为该用户设备选择正确的用户面服务节点,该用户面服务节点例如UMTS网络中的网关GPRS支持节点(Gateway GPRS Support Node,简称GGSN),或EPC网络中的服务网关(Server-Gateway,简称S-GW)/PDN网关(Public Data Network-Gateway,简称P-GW),或者,当某个用户设备选择了错误的控制面服务节点时,为用户设备再选择正确的控制面服务节点。
现有技术中,核心网的控制面服务节点根据用户设备的使用类型(Usage Type)为不同用户设备选择用户面服务节点或者另一控制面服务节点。具体地,核心网的控制面服务节点根据获取到的用户设备的使用类型,在对应的域名***(Domain Name System,简称DNS)中查询符合该使用类型的用户面服务节点或者控制面服务节点。
但是,采用现有技术所选择的用户面服务节点或者控制面服务节点经常无法满足用户设备的实际业务需求,从而导致业务失败。
发明内容
本发明实施例提供一种服务节点选择、查询方法,装置及***,用以满足用户设备的实际业务需求。
本发明实施例第一方面提供一种服务节点选择方法,包括:
接收UE发送的请求消息,并根据该请求消息获取UE的使用类型以及选择辅助信息,其中,选择辅助信息包括专网类型和业务属性信息中的至少一种;进而,根据所获得的使用类型和选择辅助信息来确定为UE服务的服务节点。通过这种方式所选择到的服务节点是支持UE的专网类型并且能够满足UE本次所请求的业务的服务节点,因此能够保证UE的业务成功。
在一种可能的设计中,上述根据请求消息获取UE的使用类型以及选择辅助信息的方法为:
从所述请求消息中获取所述使用类型和选择辅助信息;或者,
从所述请求消息中获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型。
在一种可能的设计中,上述根据请求消息获取UE的使用类型以及选择辅助信息的另一方法为:
从所述UE的签约数据中获取所述使用类型,从所述请求消息中获取选择辅助信息;或者,
从所述UE的签约数据中获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型;或者,
从所述UE的签约数据中获取所述使用类型以及所述业务属性信息。
在一种可能的设计中,上述根据请求消息获取UE的使用类型以及选择辅助信息的另一方法为:
通过所述UE的上下文获取所述使用类型,从所述请求消息中获取选择辅助信息;或者,
通过所述UE的上下文获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型;或者,
通过所述UE的上下文获取所述使用类型,从所述UE的签约数据中获取所述业务属性信息。
本发明实施例提供以上多种方法来获取使用类型和选择辅助信息,使得控制面实体可以根据实际情况灵活选择获取方式,以提升获取效率。
在一种可能的设计中,上述根据使用类型和选择辅助信息确定所需选择的服务节点的一种方法为:
根据所述使用类型和所述选择辅助信息,通过DNS确定所需选择的服务节点。
该方法具体可以为:
向所述DNS发送服务节点查询消息,所述服务节点查询消息中包括所述使用类型和所述选择辅助信息;
接收所述DNS发送的查询响应消息,所述查询响应消息中包括所述DNS根据所述使用类型和所述选择辅助信息查询得到的为UE服务的服务节点的服务节点标识。
在一种可能的设计中,上述根据使用类型和选择辅助信息确定所需选择的服务节点的另一种方法为:
根据所述使用类型,通过DNS获取至少一个服务节点标识以及所述服务节点标识与选择辅助信息的对应关系;
根据所述选择辅助信息以及所述服务节点标识与选择辅助信息的对应关系,从所述至少一个服务节点的服务节点标识中确定为所述UE服务的服务节点的服务节点标识。
该方法中通过DNS获取至少一个服务节点标识以及所述服务节点标识与选择辅助信息的对应关系的具体过程可以为:
向所述DNS发送服务节点查询消息,所述服务节点查询消息中包括所述使用类型;
接收所述DNS发送的查询响应消息,所述查询响应消息中包括所述DNS根据所述使用类型查询得到的至少一个服务节点的服务节点标识以及所述服务节点标识与选择辅助信息的对应关系。
在一种可能的设计中,上述根据使用类型和选择辅助信息确定所需选择的服务节点的另一种方法为:
根据所述使用类型以及所述选择辅助信息,确定可供选择的服务节点;
根据网络拓扑信息从所述可供选择的服务节点中确定地理位置距离所述UE最近的服务节点。
在一种可能的设计中,所述网络拓扑信息包括所述UE所在小区标识和/或服务节点拓扑信息。
本发明第二方面提供一种服务节点查询方法,包括:
接收控制面实体发送的服务节点查询消息,该服务节点查询消息中包括UE的使用类型和选择辅助信息,其中,选择辅助信息包括专网类型和业务属性信息中的至少一种;进而,根据接收到的使用类型和选择辅助信息,获取为UE服务的服务节点的服务节点标识;之后,向控制面实体发送查询响应消息,该查询响应消息中包括为UE服务的服务节点的服务节点标识。
在一种可能的设计中,所述根据所述使用类型和所述选择辅助信息,获取所需选择的服务节点的服务节点标识,包括:
根据所述使用类型和所述选择辅助信息,在预设映射表中查询与所述使用类型和所述选择辅助信息对应的服务节点的服务节点标识,所述映射表用于记录所述使用类型、所述选择辅助信息以及所述服务节点标识的对应关系。
本发明第三方面提供一种控制面实体,包括:
接收模块,用于接收用户设备UE发送的请求消息;
处理模块,用于根据所述请求消息,获取所述UE的使用类型以及选择辅助信息,所述选择辅助信息包括专网类型和业务属性信息中的至少一种;以及,
根据所述使用类型和所述选择辅助信息,确定为所述UE服务的服务节点。
在一种可能的设计中,所述处理模块具体用于:
从所述请求消息中获取所述使用类型和选择辅助信息;或者,
从所述请求消息中获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型。
在一种可能的设计中,所述处理模块具体还用于:
从所述UE的签约数据中获取所述使用类型,从所述请求消息中获取选择辅助信息;或者,
从所述UE的签约数据中获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型;或者,
从所述UE的签约数据中获取所述使用类型以及所述业务属性信息。
在一种可能的设计中,所述处理模块具体还用于:
通过所述UE的上下文获取所述使用类型,从所述请求消息中获取选择辅助信息;或者,
通过所述UE的上下文获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型;或者,
通过所述UE的上下文获取所述使用类型,从所述UE的签约数据中获取所述业务属性信息。
在一种可能的设计中,所述处理模块具体还用于:
根据所述使用类型和所述选择辅助信息,通过域名***DNS确定所需选择的服务节点。
在一种可能的设计中,所述处理模块包括:
第一发送单元,用于向所述DNS发送服务节点查询消息,所述服务节点查询消息中包括所述使用类型和所述选择辅助信息;
第一接收单元,用于接收所述DNS发送的查询响应消息,所述查询响应消息中包括所述DNS根据所述使用类型和所述选择辅助信息查询得到的为UE服务的服务节点的服务节点标识。
在一种可能的设计中,所述处理模块具体还用于:
根据所述使用类型,通过域名***DNS获取至少一个服务节点标识以及所述服务节点标识与选择辅助信息的对应关系;根据所述选择辅助信息以及所述服务节点标识与选择辅助信息的对应关系,从所述至少一个服务节点的服务节点标识中确定为所述UE服务的服务节点的服务节点标识。
在一种可能的设计中,所述处理模块还包括:
第二发送单元,用于向所述DNS发送服务节点查询消息,所述服务节点查询消息中包括所述使用类型;
第二接收单元,用于接收所述DNS发送的查询响应消息,所述查询响应消息中包括所述DNS根据所述使用类型查询得到的至少一个服务节点的服务节点标识以及所述服务节点标识与选择辅助信息的对应关系。
在一种可能的设计中,所述处理模块具体还用于:
根据所述使用类型以及所述选择辅助信息,确定可供选择的服务节点;以及,根据网络拓扑信息从所述可供选择的服务节点中确定地理位置距离所述UE最近的服务节点。
在一种可能的设计中,所述网络拓扑信息包括所述UE所在小区标识和/或服务节点拓扑信息。
在一种可能的设计中,所述业务属性信息包括所述UE需要访问的接入点名称APN、所述UE的服务请求类型、所述UE需要访问的应用服务器域名以及所述UE需要访问的应用服务器IP地址中的至少一种。
在一种可能的设计中,所述请求消息具体为Attach消息、TAU消息,或者PDN建立消息。
本发明第四方面提供一种域名***,包括:
接收模块,用于接收控制面实体发送的服务节点查询消息,所述服务节点查询消息中包括用户设备UE的使用类型和选择辅助信息,所述选择辅助信息包括专网类型和业务属性信息中的至少一种;
处理模块,用于根据所述使用类型和所述选择辅助信息,获取为所述UE服务的服务节点的服务节点标识;
发送模块,用于向所述控制面实体发送查询响应消息,所述查询响应消息中包括为所述UE服务的服务节点的服务节点标识。
在一种可能的设计中,所述处理模块具体用于:
根据所述使用类型和所述选择辅助信息,在预设映射表中查询与所述使用类型和所述选择辅助信息对应的服务节点的服务节点标识,所述映射表用于记录所述使用类型、所述选择辅助信息以及所述服务节点标识的对应关系。
本发明第五方面提供一种控制面实体,包括存储器和处理器;
存储器用于存储程序指令,处理器用于调用存储器中的程序指令,执行下述方法:
接收用户设备UE发送的请求消息;
根据所述请求消息,获取所述UE的使用类型以及选择辅助信息,所述选择辅助信息包括专网类型和业务属性信息中的至少一种;
根据所述使用类型和所述选择辅助信息,确定为所述UE服务的服务节
点。
在一种可能的设计中,处理器还用于:
从请求消息中获取使用类型和选择辅助信息;或者,
从请求消息中获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型。
在一种可能的设计中,处理器还用于:
从UE的签约数据中获取使用类型,从请求消息中获取选择辅助信息;或者,
从UE的签约数据中获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型;或者,
从UE的签约数据中获取使用类型以及业务属性信息。
在一种可能的设计中,处理器还用于:
通过UE的上下文获取使用类型,从请求消息中获取选择辅助信息;或者,
通过UE的上下文获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型;或者,
通过UE的上下文获取使用类型,从UE的签约数据中获取业务属性信息。
在一种可能的设计中,处理器还用于:
根据所述使用类型和所述选择辅助信息,通过DNS确定所需选择的服务节点。
在一种可能的设计中,处理器还用于:
向DNS发送服务节点查询消息,该服务节点查询消息中包括使用类型和选择辅助信息。
接收DNS发送的查询响应消息,该查询响应消息中包括DNS根据使用类型和选择辅助信息查询得到的为UE服务的服务节点的服务节点标识。
在一种可能的设计中,处理器还用于:
根据所述使用类型,通过DNS获取至少一个服务节点标识以及服务节点标识与选择辅助信息的对应关系;根据选择辅助信息以及服务节点标识与选择辅助信息的对应关系,从至少一个服务节点的服务节点标识中确定为UE服务的服务节点的服务节点标识。
在一种可能的设计中,处理器还用于:
向DNS发送服务节点查询消息,该服务节点查询消息中包括使用类型。
接收DNS发送的查询响应消息,该查询响应消息中包括DNS根据使用类型查询得到的至少一个服务节点的服务节点标识以及服务节点标识与选择辅助信息的对应关系。
在一种可能的设计中,处理器还用于:
根据使用类型以及选择辅助信息,确定可供选择的服务节点;以及,根据网络拓扑信息从可供选择的服务节点中确定地理位置距离UE最近的服务节点。
在一种可能的设计中,上述网络拓扑信息包括UE所在小区标识和/或服务节点拓扑信息。
在一种可能的设计中,业务属性信息包括所述UE需要访问的接入点名称APN、所述UE的服务请求类型、所述UE需要访问的应用服务器域名以及所述UE需要访问的应用服务器IP地址中的至少一种。
在一种可能的设计中,上述请求消息具体为Attach消息、TAU消息,或者PDN建立消息。
本发明第六发面提供一种域名***,包括存储器和处理器;
存储器用于存储程序指令,处理器用于调用存储器中的程序指令,执行下述方法:
接收控制面实体发送的服务节点查询消息,该服务节点查询消息中包括UE的使用类型和选择辅助信息,该选择辅助信息包括专网类型和业务属性信息中的至少一种。
根据使用类型和选择辅助信息,获取为UE服务的服务节点的服务节点标识。
向控制面实体发送查询响应消息,该查询响应消息中包括为UE服务的服务节点的服务节点标识。
在一种可能的设计中,处理器具体用于:
根据使用类型和选择辅助信息,在预设映射表中查询与使用类型和选择辅助信息对应的服务节点的服务节点标识,该映射表用于记录使用类型、选择辅助信息以及服务节点标识的对应关系
使用本发明实施例的方案,能够基于使用类型和选择辅助信息来选择为UE服务的服务节点,从而保证了UE的业务成功。
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍,显而易见地,下面描述中的附图是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1为本发明提供的服务节点选择方法的架构示意图;
图2为本发明提供的服务节点选择方法实施例一的流程示意图;
图3为本发明提供的服务节点选择方法实施例二的流程示意图;
图4为本发明提供的服务节点选择方法实施例三的流程示意图;
图5为本发明提供的服务节点选择方法的示例流程图;
图6为本发明实施例提供的控制面实体实施例一的模块结构图;
图7为本发明实施例提供的控制面实体实施例二的模块结构图;
图8为本发明实施例提供的控制面实体实施例三的模块结构图;
图9为本发明实施例提供的控制面实体实施例四的模块结构图;
图10为本发明实施例提供的域名***实施例一的模块结构图;
图11为本发明实施例提供的域名***实施例二的模块结构图。
为使本发明实施例的目的、技术方案和优点更加清楚,下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
在3GPP通信***中,由于核心网可以同时支持多种不同类型的UE,则核心网的控制面服务节点(例如UMTS网络中的SGSN,或EPC网络中的MME)和用户面服务节点(例如UMTS网络中的GGSN,或EPC网络中的
S-GW/P-GW)也必须能够支持多种不同类型的UE。一方面,对于控制面服务节点来说,由于UE在接入网络时可能会接入到错误的控制面服务节点(也就是说,UE所接入的服务节点不能够服务UE),那么这个控制面服务节点需要为UE选择正确的控制面服务节点,并将UE重定向到正确的(能够服务该UE的)控制面服务节点。另一方面,对于用户面服务节点,由于各种业务对服务等级协议(Service-Level Agreement,简称SLA)不同的需求,用户面服务节点可能在物理上或逻辑上都无法合一。举例来说,网页浏览等用户业务对时延,速率等都要求不高,所以用户面服务节点的部署位置贴近核心网侧,这样可以避免用户在移动时用户面服务节点的频繁切换。但超低时延通信等用户业务对时延很敏感,必须要求用户面服务节点的部署位置更为贴近UE侧,来保证业务的时延要求。因此,核心网中存在多种不同类型、不同部署位置的用户面服务节点,需要根据UE的具体业务需求来选择用户面服务节点。
本发明基于上述需求,提出一种选择能够服务UE的最优服务节点的方法。
其中,本发明中所指的控制面服务节点和用户面服务节点的具体含义为:
控制面服务节点:是指3GPP通信***中提供控制面业务的网元。同一个控制面服务节点可以同时配置支持多种不同类型或不同业务的UE,并为这些UE提供相应的服务,例如根据用户类型而定制的移动管理服务,安全服务,承载管理服务等等。目前3GPP通信***中,MME为4G架构下的控制面服务节点,SGSN为3G架构下的控制面服务节点。需要说明的是,如果5G架构下存在专用网络或网络切片,则5G的专用网络或网络切片中的控制面服务节点也应在本发明保护范围内。
用户面服务节点:是指3GPP通信***中提供用户面业务的网元。网络中存在多种不同类型和不同部署位置的用户面服务节点,每个用户面服务节点可以针对于某一类应用场景或用户需求提供服务。需要说明的是,包括但不限于4G网络中的S-GW,PDN-GW,以及5G网络中为UE提供用户面业务的网络实体或功能。举例来说,当前EPC网络中的S-GW和P-GW就可以认为是MBB业务的用户面服务节点。在5G中,网络中可能会存在新的网络实体或功能作为用户面服务节点来提供其他新业务,如超低时延通信业务,都属于本
发明所指的用户面服务节点。
图1为本发明提供的服务节点选择方法的架构示意图,如图1所示,网络中存在多种不同类型和不同部署位置的用户面服务节点,每个用户面服务节点可以针对于某一类应用场景或用户需求提供服务,UE通过控制面服务节点来选择可以为自身服务的用户面服务节点。
图2为本发明提供的服务节点选择方法实施例一的流程示意图,如图2所示,该方法的执行主体为控制面实体。其中,该控制面实体可以是实际服务UE的控制面服务节点,也可以是接收到UE请求的控制面节点,例如MME、SGSN、或者是5G网络中的执行控制面功能的实体。该方法包括:
S101、接收用户设备UE发送的请求消息。
UE发送的请求消息可以是Attach消息,TAU消息,或者是PDN建立消息或其他与用户面建立承载相关的消息。即只要是能够触发控制面实体进行服务节点选择的消息,都可以称为UE的请求消息。
其中,Attach消息为附着消息,TAU消息为跟踪区更新消息,PDN建立消息为PDN Connectivity Req消息。
S102、根据上述请求消息,获取UE的使用类型以及选择辅助信息,该选择辅助信息包括专网类型和业务属性信息中的至少一种。
其中,使用类型为Usage Type。
专网类型为UE在签约或在网络注册后,由网络根据UE的具体类型和能力和/或网络的本地策略以及具体部署方式等为UE分配的专用核心网的类型。优选地,专网类型为DCN Type。
业务属性信息与UE所请求的业务/服务相对应,用于指定UE此次请求所希望获取的业务/服务。业务属性信息包括但不限于UE需要访问的接入点名称(Access Point Name,简称APN)、UE的服务请求类型Service Type、UE需要访问的应用服务器域名以及UE需要访问的应用服务器IP地址。
需要说明的是,UE的使用类型和专网类型是UE自身的属性,并不能标识UE的具体业务请求,而UE的业务属性信息可以标识UE的具体业务请求。举例来说,一个UE的使用类型可以是MBB类型,专网类型可以是MBB DCN类型。该UE可以有多种业务需求,例如语音通信,短消息通信,超可靠性通信,超低时延通信等等,而这些业务需求使用业务属性来描述。
S103、根据上述使用类型和选择辅助信息,确定为UE服务的服务节点。
上述服务节点既可以是控制面服务节点,也可以是用户面服务节点。即控制面实体根据UE的实际需要,选择出为UE服务的控制面服务节点或用户面服务节点。
进一步地,在确定出为UE服务的服务节点后,如果当前控制面实体选择了另一个控制面实体,即当前的控制面实体并不能服务UE,则当前控制面实体会发起重定向过程,将UE重定向到能够服务UE的控制面实体。例如将另一个控制面实体的标识发送给接入网节点,由接入网节点根据该标识将UE重定向。
如果当前控制面实体选择了用户面服务节点,则当前控制面实体会向所选的用户面服务节点发送会话建立请求或承载建立请求,以为UE建立用户面承载。
本实施例中,控制面实体根据UE的使用类型和选择辅助信息来选择为UE服务的服务节点,即在使用类型的基础上,还会根据UE的专网类型和/或业务属性信息来选择服务节点,从而使得所选择到的服务节点是支持UE的专网类型,并且能够满足UE本次的所请求的业务的服务节点,进而保证了UE的业务成功。
另一实施例中,在上述步骤S102中根据UE的请求消息获取UE的使用类型和选择辅助信息的具体方式如下:
对于使用类型,可以从上述请求消息中直接获取,即请求消息中会直接携带使用类型;或者,也可以通过查询UE的签约数据来获取使用类型;或者,也可以通过UE的上下文获取使用类型。通过查询UE的签约数据来获取使用类型的方法可以参考现有技术,此处不再赘述。
对于专网类型,可以从上述请求消息中直接获取,即请求消息中会直接携带专网类型;或者,也可以根据预设的使用类型与专网类型的对应关系以及使用类型来获取专网类型。
对于业务属性信息,可以从上述请求消息中获取,即请求消息中会直接携带业务属性信息;或者,也可以通过查询UE的签约数据来获取业务属性信息。
基于上述获取方式,上述步骤S102中获取使用类型和选择辅助信息的方法具体可以包括:
1、若选择辅助信息仅为专网类型,则可以通过以下至少一种方式来获取:
(1)从请求消息中获取使用类型和专网类型;
(2)从请求消息中获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型来获取专网类型;
(3)从UE的签约数据中获取使用类型,从请求消息中获取专网类型;
在此之前,需要首先获取到UE的签约数据。
UE的签约数据可以通过控制面实体通过位置更新update location过程从归属签约用户服务器(Home Subscriber Server,简称HSS)中获取。控制面实体在发送的位置更新请求消息中包含UE的标识,HSS向控制面实体返回位置更新响应消息,其中包含对应该UE的标识的签约数据。
以下获取UE的签约数据的方法都与此相同,不再赘述。
(4)从UE的签约数据中获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型来获取专网类型;
(5)通过UE的上下文获取使用类型,从请求消息中获取专网类型;
在此之前,需要首先获取到UE的上下文。
具体地,控制面实体会向之前服务UE的控制面实体发送获取上下文请求,其中包含UE ID,原控制面实体返回获取上下文响应消息,其中包含UE上下文,UE上下文中包含UE的使用类型。控制面实体再从UE上下文获取UE的使用类型。
以下获取UE的上下文的方法都与此相同,不再赘述。
(6)通过UE的上下文获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型来获取专网类型。
2、若选择辅助信息仅为业务属性信息,则可以通过以下至少一种方式来获取:
(1)从请求消息中获取使用类型和业务属性类型;
(2)从请求消息中获取使用类型,从UE的签约数据中获取业务属性信息;
(3)从UE的签约数据中获取使用类型,从请求消息中获取业务属性信息;
(4)从UE的签约数据中获取使用类型和业务属性信息;
(5)通过UE的上下文获取使用类型,从请求消息中获取业务属性信息;
(6)通过UE的上下文获取使用类型,从UE的签约数据中获取业务属性信息。
3、若选择辅助信息为专网类型和业务属性信息,上述步骤S102的获取方式为上述1和2中各种方法基础上的进一步组合,此处不再赘述,但是只要是能从上述1和2中各方法推导出的组合,都属于本发明保护的范围。
在上述实施例的基础上,本实施例涉及根据使用类型和选择辅助信息确定所需选择的服务节点的过程。
具体地,根据使用类型和选择辅助信息,通过DNS确定所需选择的服务节点。
图3为本发明提供的服务节点选择方法实施例二的流程示意图,如图3所示,上述通过DNS确定所需选择的服务节点的具体过程为:
S201、控制面实体向域名***DNS发送服务节点查询消息。
该服务节点查询消息中包括上述使用类型和选择辅助信息。
S202、DNS接收控制面实体发送的服务节点查询消息。
该服务节点查询消息中包括UE的使用类型和选择辅助信息,该选择辅助信息包括专网类型和业务属性信息中的至少一种。
S203、DNS根据使用类型和选择辅助信息,获取为UE服务的服务节点的服务节点标识。
S204、DNS向控制面实体发送查询响应消息。
该查询响应消息中包括为UE服务的服务节点的服务节点标识。
S205、控制面实体接收DNS发送的查询响应消息。该查询响应消息中包括DNS根据上述使用类型和选择辅助信息查询得到的为UE服务的服务节点的服务节点标识。
本实施例中,当获取到UE的使用类型和选择辅助信息后,将这些信息发送给DNS,在DNS中保存有不同使用类型、选择辅助信息与服务节点的对应关系,DNS根据这些信息查询到满足UE本次请求的服务节点后,将所选择到的为UE服务的服务节点标识返回。从而实现准确选择出服务节点。
另一实施例中,上述步骤S203具体包括:
根据使用类型和选择辅助信息,在预设映射表中查询与使用类型和选择辅助信息对应的服务节点的服务节点标识,该映射表用于记录使用类型、选
择辅助信息以及服务节点标识的对应关系。
在上述实施例的基础上,本实施例涉及根据使用类型和选择辅助信息确定所需选择的服务节点的另一种方法。
具体地,根据使用类型,通过DNS获取至少一个服务节点标识以及服务节点标识与选择辅助信息的对应关系;并且,
根据选择辅助信息以及服务节点标识与选择辅助信息的对应关系,从上述至少一个服务节点的服务节点标识中确定为UE服务的服务节点的服务节点标识。
图4为本发明提供的服务节点选择方法实施例三的流程示意图,如图4所示,上述通过DNS获取至少一个服务节点标识以及服务节点标识与选择辅助信息的对应关系的具体过程为:
S301、控制面实体向DNS发送服务节点查询消息,该服务节点查询消息中包括使用类型。
S302、DNS接收控制面实体发送的服务节点查询消息。
该服务节点查询消息中包括UE的使用类型。
S303、DNS根据使用类型,获取至少一个服务节点的服务节点标识。
S304、DNS向控制面实体发送查询响应消息。该查询响应消息中包括至少一个服务节点的服务节点标识以及服务节点标识与选择辅助信息的对应关系。
S305、控制面实体接收DNS发送的查询响应消息。
该查询响应消息中包括DNS根据使用类型查询得到的至少一个服务节点的服务节点标识以及服务节点标识与选择辅助信息的对应关系。
S306、控制面实体根据选择辅助信息以及服务节点标识与选择辅助信息的对应关系,从上述至少一个服务节点的服务节点标识中确定为UE服务的服务节点的服务节点标识。
本实施例中,控制面服务节点仅向DNS发送使用类型,进而在根据DNS的查询结果,再结合选择辅助信息,确定出为UE服务的服务节点。本实施例中,DNS侧不需要做任何的改动,而通过控制面服务节点自身来选择为UE服务的服务节点,从而减少了网元变动,提高了执行效率。
在前述实施例的基础上,即根据使用类型和选择辅助信息确定出可供选
择的服务节点的基础上,控制面实体还可以进一步结合当前的网络拓扑再选择出更优的服务节点。
具体地,在根据使用类型和选择辅助信息确定出可供选择的服务节点后,再根据网络拓扑信息从上述可供选择的服务节点中确定地理位置距离UE最近的服务节点。
其中,如果网络拓扑信息是UE小区标识,则可以由接入网节点在转发UE请求消息时上报给控制面实体。如果网络拓扑信息是服务节点拓扑信息,则可以在控制面实体中预配置。
可选地,上述网络拓扑信息包括UE所在小区标识和/或用户面服务节点拓扑信息。
具体实施过程中,假如都是通过DNS来查询服务节点标识,则可以将使用类型、选择辅助信息和网络拓扑信息统一发送给DNS,由DNS来统一进行查询。或者,也可以和DNS进行多次交互,根据每次交互的结果来确定是否需要再进行查询。本发明对此不做限制。
图5为本发明提供的服务节点选择方法的示例流程图,图5以控制面服务节点为执行主体,选择辅助信息仅为专网类型,并且专网类型在请求消息中携带为例,如图5所示,服务节点选择的过程为:
S401、UE向控制面服务节点发送请求消息,该请求消息中包括专网类型。
UE的请求消息中也包括UE的标识。
S402、控制面服务节点从UE的签约数据中获取UE的使用类型。
其中,UE的签约数据可以通过位置更新update location过程从归属签约用户服务器(Home Subscriber Server,简称HSS)中获取。控制面服务节点在发送的位置更新请求消息中包含已获取的UE的标识,HSS向控制面服务节点返回位置更新响应消息,其中包含对应该UE的标识的签约数据。控制面服务节点再根据UE的标识从UE的签约数据中获取UE的使用类型。
S403、控制面服务节点向DNS发送服务节点查询消息。
该服务节点查询消息中包括使用类型和专网类型。
S404、DNS根据使用类型和专网类型,获取为UE服务的服务节点的服务节点标识。
S405、DNS向控制面服务节点发送查询响应消息。
该查询响应消息中包括为UE服务的服务节点的服务节点标识。
根据上述为UE服务的服务节点的服务节点标识,控制面服务节点可以为UE建立用户面承载。
图6为本发明实施例提供的控制面实体实施例一的模块结构图,如图6所示,该控制面实体包括:
接收模块601,用于接收UE发送的请求消息。
处理模块602,用于根据请求消息,获取UE的使用类型以及选择辅助信息,该选择辅助信息包括专网类型和业务属性信息中的至少一种;以及,
根据使用类型和选择辅助信息,确定为UE服务的服务节点。
该控制面实体用于实现前述方法实施例,其实现原理和技术效果类似,此处不再赘述。
另一实施例中,处理模块602具体用于:
从请求消息中获取使用类型和选择辅助信息;或者,
从请求消息中获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型。
另一实施例中,处理模块602具体还用于:
从UE的签约数据中获取使用类型,从请求消息中获取选择辅助信息;或者,
从UE的签约数据中获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型;或者,
从UE的签约数据中获取使用类型以及业务属性信息。
另一实施例中,处理模块602具体还用于:
通过UE的上下文获取使用类型,从请求消息中获取选择辅助信息;或者,
通过UE的上下文获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型;或者,
通过UE的上下文获取使用类型,从UE的签约数据中获取业务属性信息。
另一实施例中,处理模块602具体还用于:
根据所述使用类型和所述选择辅助信息,通过DNS确定所需选择的服务节点。
图7为本发明实施例提供的控制面实体实施例二的模块结构图,如图7所示,处理模块602包括:
第一发送单元6021,用于向DNS发送服务节点查询消息,该服务节点查询消息中包括使用类型和选择辅助信息。
第一接收单元6022,用于接收DNS发送的查询响应消息,该查询响应消息中包括DNS根据使用类型和选择辅助信息查询得到的为UE服务的服务节点的服务节点标识。
另一实施例中,处理模块602具体还用于:
根据所述使用类型,通过DNS获取至少一个服务节点标识以及服务节点标识与选择辅助信息的对应关系;根据选择辅助信息以及服务节点标识与选择辅助信息的对应关系,从至少一个服务节点的服务节点标识中确定为UE服务的服务节点的服务节点标识。
图8为本发明实施例提供的控制面实体实施例三的模块结构图,如图8所示,在图7的基础上,处理模块602还包括:
第二发送单元6023,用于向DNS发送服务节点查询消息,该服务节点查询消息中包括使用类型。
第二接收单元6024,用于接收DNS发送的查询响应消息,该查询响应消息中包括DNS根据使用类型查询得到的至少一个服务节点的服务节点标识以及服务节点标识与选择辅助信息的对应关系。
另一实施例中,处理模块602具体还用于:
根据使用类型以及选择辅助信息,确定可供选择的服务节点;以及,根据网络拓扑信息从可供选择的服务节点中确定地理位置距离UE最近的服务节点。
另一实施例中,上述网络拓扑信息包括UE所在小区标识和/或服务节点拓扑信息。业务属性信息包括所述UE需要访问的接入点名称APN、所述UE的服务请求类型、所述UE需要访问的应用服务器域名以及所述UE需要访问的应用服务器IP地址中的至少一种。
另一实施例中,上述请求消息具体为Attach消息、TAU消息,或者PDN建立消息。
图9为本发明实施例提供的控制面实体实施例四的模块结构图,如图9
所示,该控制面实体包括存储器701和处理器702。
存储器701用于存储程序指令,处理器702用于调用存储器701中的程序指令,执行下述方法:
接收用户设备UE发送的请求消息;
根据所述请求消息,获取所述UE的使用类型以及选择辅助信息,所述选择辅助信息包括专网类型和业务属性信息中的至少一种;
根据所述使用类型和所述选择辅助信息,确定为所述UE服务的服务节点。
进一步地,处理器702还用于:
从请求消息中获取使用类型和选择辅助信息;或者,
从请求消息中获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型。
进一步地,处理器702还用于:
从UE的签约数据中获取使用类型,从请求消息中获取选择辅助信息;或者,
从UE的签约数据中获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型;或者,
从UE的签约数据中获取使用类型以及业务属性信息。
进一步地,处理器702还用于:
通过UE的上下文获取使用类型,从请求消息中获取选择辅助信息;或者,
通过UE的上下文获取使用类型,并根据预设的使用类型与专网类型的对应关系以及使用类型,获取专网类型;或者,
通过UE的上下文获取使用类型,从UE的签约数据中获取业务属性信息。
进一步地,处理器702还用于:
根据所述使用类型和所述选择辅助信息,通过DNS确定所需选择的服务节点。
进一步地,处理器702还用于:
向DNS发送服务节点查询消息,该服务节点查询消息中包括使用类型和选择辅助信息。
接收DNS发送的查询响应消息,该查询响应消息中包括DNS根据使用类型和选择辅助信息查询得到的为UE服务的服务节点的服务节点标识。
进一步地,处理器702还用于:
根据所述使用类型,通过DNS获取至少一个服务节点标识以及服务节点标识与选择辅助信息的对应关系;根据选择辅助信息以及服务节点标识与选择辅助信息的对应关系,从至少一个服务节点的服务节点标识中确定为UE服务的服务节点的服务节点标识。
进一步地,处理器702还用于:
向DNS发送服务节点查询消息,该服务节点查询消息中包括使用类型。
接收DNS发送的查询响应消息,该查询响应消息中包括DNS根据使用类型查询得到的至少一个服务节点的服务节点标识以及服务节点标识与选择辅助信息的对应关系。
进一步地,处理器702还用于:
根据使用类型以及选择辅助信息,确定可供选择的服务节点;以及,根据网络拓扑信息从可供选择的服务节点中确定地理位置距离UE最近的服务节点。
另一实施例中,上述网络拓扑信息包括UE所在小区标识和/或服务节点拓扑信息。
另一实施例中,业务属性信息包括所述UE需要访问的接入点名称APN、所述UE的服务请求类型、所述UE需要访问的应用服务器域名以及所述UE需要访问的应用服务器IP地址中的至少一种。
另一实施例中,上述请求消息具体为Attach消息、TAU消息,或者PDN建立消息。
图10为本发明实施例提供的域名***实施例一的模块结构图,如图10所示,该域名***包括:
接收模块801,用于接收控制面实体发送的服务节点查询消息,该服务节点查询消息中包括UE的使用类型和选择辅助信息,该选择辅助信息包括专网类型和业务属性信息中的至少一种。
处理模块802,用于根据使用类型和选择辅助信息,获取为UE服务的服务节点的服务节点标识。
发送模块803,用于向控制面实体发送查询响应消息,该查询响应消息中包括为UE服务的服务节点的服务节点标识。
该域名***用于实现前述方法实施例,其实现原理和技术效果类似,此处不再赘述。
另一实施例中,处理模块802具体用于:
根据使用类型和选择辅助信息,在预设映射表中查询与使用类型和选择辅助信息对应的服务节点的服务节点标识,该映射表用于记录使用类型、选择辅助信息以及服务节点标识的对应关系。
图11为本发明实施例提供的域名***实施例二的模块结构图,如图11所示,该域名***包括存储器901和处理器902。
存储器901用于存储程序指令,处理器902用于调用存储器901中的程序指令,执行下述方法:
接收控制面实体发送的服务节点查询消息,该服务节点查询消息中包括UE的使用类型和选择辅助信息,该选择辅助信息包括专网类型和业务属性信息中的至少一种。
根据使用类型和选择辅助信息,获取为UE服务的服务节点的服务节点标识。
向控制面实体发送查询响应消息,该查询响应消息中包括为UE服务的服务节点的服务节点标识。
进一步地,处理器902具体用于:
根据使用类型和选择辅助信息,在预设映射表中查询与使用类型和选择辅助信息对应的服务节点的服务节点标识,该映射表用于记录使用类型、选择辅助信息以及服务节点标识的对应关系。
本领域普通技术人员可以理解:实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成,前述的程序可以存储于一计算机可读取存储介质中,该程序在执行时,执行包括上述方法实施例的步骤;而前述的存储介质包括:ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是:以上各实施例仅用以说明本发明的技术方案,而非对其限制;尽管参照前述各实施例对本发明进行了详细的说明,本领域的普通
技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分或者全部技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。
Claims (28)
- 一种服务节点选择方法,其特征在于,包括:接收用户设备UE发送的请求消息;根据所述请求消息,获取所述UE的使用类型以及选择辅助信息,所述选择辅助信息包括专网类型和业务属性信息中的至少一种;根据所述使用类型和所述选择辅助信息,确定为所述UE服务的服务节点。
- 根据权利要求1所述的方法,其特征在于,所述根据所述请求消息,获取所述UE的使用类型以及选择辅助信息,包括:从所述请求消息中获取所述使用类型和选择辅助信息;或者,从所述请求消息中获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型。
- 根据权利要求1所述的方法,其特征在于,所述根据所述请求消息,获取所述UE的使用类型以及选择辅助信息,包括:从所述UE的签约数据中获取所述使用类型,从所述请求消息中获取选择辅助信息;或者,从所述UE的签约数据中获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型;或者,从所述UE的签约数据中获取所述使用类型以及所述业务属性信息。
- 根据权利要求1所述的方法,其特征在于,所述根据所述请求消息,获取所述UE的使用类型以及选择辅助信息,包括:通过所述UE的上下文获取所述使用类型,从所述请求消息中获取选择辅助信息;或者,通过所述UE的上下文获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型;或者,通过所述UE的上下文获取所述使用类型,从所述UE的签约数据中获取所述业务属性信息。
- 根据权利要求1-4任一项所述的方法,其特征在于,所述根据所述使用类型和所述选择辅助信息,确定所需选择的服务节点,包括:根据所述使用类型和所述选择辅助信息,通过域名***DNS确定所需选 择的服务节点。
- 根据权利要求5所述的方法,其特征在于,所述通过域名***DNS确定所需选择的服务节点,包括:向所述DNS发送服务节点查询消息,所述服务节点查询消息中包括所述使用类型和所述选择辅助信息;接收所述DNS发送的查询响应消息,所述查询响应消息中包括所述DNS根据所述使用类型和所述选择辅助信息查询得到的为UE服务的服务节点的服务节点标识。
- 根据权利要求1-4任一项所述的方法,其特征在于,所述根据所述使用类型和所述选择辅助信息,确定所需选择的服务节点,包括:根据所述使用类型,通过域名***DNS获取至少一个服务节点标识以及所述服务节点标识与选择辅助信息的对应关系;根据所述选择辅助信息以及所述服务节点标识与选择辅助信息的对应关系,从所述至少一个服务节点的服务节点标识中确定为所述UE服务的服务节点的服务节点标识。
- 根据权利要求7所述的方法,其特征在于,所述通过域名***DNS获取至少一个服务节点标识以及所述服务节点标识与选择辅助信息的对应关系,包括:向所述DNS发送服务节点查询消息,所述服务节点查询消息中包括所述使用类型;接收所述DNS发送的查询响应消息,所述查询响应消息中包括所述DNS根据所述使用类型查询得到的至少一个服务节点的服务节点标识以及所述服务节点标识与选择辅助信息的对应关系。
- 根据权利要求1-8任一项所述的方法,其特征在于,所述根据所述使用类型和所述选择辅助信息,确定为所述UE服务的服务节点,包括:根据所述使用类型以及所述选择辅助信息,确定可供选择的服务节点;根据网络拓扑信息从所述可供选择的服务节点中确定地理位置距离所述UE最近的服务节点。
- 根据权利要求9所述的方法,其特征在于,所述网络拓扑信息包括所述UE所在小区标识和/或服务节点拓扑信息。
- 根据权利要求1-10任一项所述的方法,其特征在于,所述业务属性信息包括所述UE需要访问的接入点名称APN、所述UE的服务请求类型、所述UE需要访问的应用服务器域名以及所述UE需要访问的应用服务器IP地址中的至少一种。
- 根据权利要求1-11任一项所述的方法,其特征在于,所述请求消息具体为Attach消息、TAU消息,或者PDN建立消息。
- 一种服务节点查询方法,其特征在于,包括:接收控制面实体发送的服务节点查询消息,所述服务节点查询消息中包括用户设备UE的使用类型和选择辅助信息,所述选择辅助信息包括专网类型和业务属性信息中的至少一种;根据所述使用类型和所述选择辅助信息,获取为所述UE服务的服务节点的服务节点标识;向所述控制面实体发送查询响应消息,所述查询响应消息中包括为所述UE服务的服务节点的服务节点标识。
- 根据权利要求13所述的方法,其特征在于,所述根据所述使用类型和所述选择辅助信息,获取所需选择的服务节点的服务节点标识,包括:根据所述使用类型和所述选择辅助信息,在预设映射表中查询与所述使用类型和所述选择辅助信息对应的服务节点的服务节点标识,所述映射表用于记录所述使用类型、所述选择辅助信息以及所述服务节点标识的对应关系。
- 一种控制面实体,其特征在于,包括:接收模块,用于接收用户设备UE发送的请求消息;处理模块,用于根据所述请求消息,获取所述UE的使用类型以及选择辅助信息,所述选择辅助信息包括专网类型和业务属性信息中的至少一种;以及,根据所述使用类型和所述选择辅助信息,确定为所述UE服务的服务节点。
- 根据权利要求15所述的控制面实体,其特征在于,所述处理模块具体用于:从所述请求消息中获取所述使用类型和选择辅助信息;或者,从所述请求消息中获取所述使用类型,并根据预设的使用类型与专网类 型的对应关系以及所述使用类型,获取所述专网类型。
- 根据权利要求15所述的控制面实体,其特征在于,所述处理模块具体还用于:从所述UE的签约数据中获取所述使用类型,从所述请求消息中获取选择辅助信息;或者,从所述UE的签约数据中获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型;或者,从所述UE的签约数据中获取所述使用类型以及所述业务属性信息。
- 根据权利要求15所述的控制面实体,其特征在于,所述处理模块具体还用于:通过所述UE的上下文获取所述使用类型,从所述请求消息中获取选择辅助信息;或者,通过所述UE的上下文获取所述使用类型,并根据预设的使用类型与专网类型的对应关系以及所述使用类型,获取所述专网类型;或者,通过所述UE的上下文获取所述使用类型,从所述UE的签约数据中获取所述业务属性信息。
- 根据权利要求15-18任一项所述的控制面实体,其特征在于,所述处理模块具体还用于:通过域名***DNS确定所需选择的服务节点,其中,所述DNS根据所述使用类型和所述选择辅助信息选择得到为UE服务的服务节点的服务节点标识。
- 根据权利要求19所述的控制面实体,其特征在于,所述处理模块包括:第一发送单元,用于向所述DNS发送服务节点查询消息,所述服务节点查询消息中包括所述使用类型和所述选择辅助信息;第一接收单元,用于接收所述DNS发送的查询响应消息,所述查询响应消息中包括所述DNS根据所述使用类型和所述选择辅助信息查询得到的为UE服务的服务节点的服务节点标识。
- 根据权利要求15-18任一项所述的控制面实体,其特征在于,所述处理模块具体还用于:通过域名***DNS获取至少一个服务节点标识以及所述服务节点标识与选择辅助信息的对应关系,其中,所述DNS根据使用类型选择得到所述至少一个服务节点标识以及所述服务节点标识与选择辅助信息的对应关系;根据所述选择辅助信息以及所述服务节点标识与选择辅助信息的对应关系,从所述至少一个服务节点的服务节点标识中确定为所述UE服务的服务节点的服务节点标识。
- 根据权利要求21所述的控制面实体,其特征在于,所述处理模块还包括:第二发送单元,用于向所述DNS发送服务节点查询消息,所述服务节点查询消息中包括所述使用类型;第二接收单元,用于接收所述DNS发送的查询响应消息,所述查询响应消息中包括所述DNS根据所述使用类型查询得到的至少一个服务节点的服务节点标识以及所述服务节点标识与选择辅助信息的对应关系。
- 根据权利要求15-22任一项所述的控制面实体,其特征在于,所述处理模块具体还用于:根据所述使用类型以及所述选择辅助信息,确定可供选择的服务节点;以及,根据网络拓扑信息从所述可供选择的服务节点中确定地理位置距离所述UE最近的服务节点。
- 根据权利要求23所述的控制面实体,其特征在于,所述网络拓扑信息包括所述UE所在小区标识和/或服务节点拓扑信息。
- 根据权利要求15-24任一项所述的控制面实体,其特征在于,所述业务属性信息包括所述UE需要访问的接入点名称APN、所述UE的服务请求类型、所述UE需要访问的应用服务器域名以及所述UE需要访问的应用服务器IP地址中的至少一种。
- 根据权利要求15-25任一项所述的控制面实体,其特征在于,所述请求消息具体为Attach消息、TAU消息,或者PDN建立消息。
- 一种域名***,其特征在于,包括:接收模块,用于接收控制面实体发送的服务节点查询消息,所述服务节点查询消息中包括用户设备UE的使用类型和选择辅助信息,所述选择辅助信息包括专网类型和业务属性信息中的至少一种;处理模块,用于根据所述使用类型和所述选择辅助信息,获取为所述UE服务的服务节点的服务节点标识;发送模块,用于向所述控制面实体发送查询响应消息,所述查询响应消息中包括为所述UE服务的服务节点的服务节点标识。
- [根据细则91更正 12.04.2016]
根据权利要求27所述的域名***,其特征在于,所述处理模块具体用于:根据所述使用类型和所述选择辅助信息,在预设映射表中查询与所述使用类型和所述选择辅助信息对应的服务节点的服务节点标识,所述映射表用于记录所述使用类型、所述选择辅助信息以及所述服务节点标识的对应关系。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP16896032.6A EP3432151A4 (en) | 2016-03-31 | 2016-03-31 | METHOD, APPARATUS AND SYSTEM FOR SELECTING AND INTERROGATION OF SERVICE NODES |
PCT/CN2016/078220 WO2017166252A1 (zh) | 2016-03-31 | 2016-03-31 | 服务节点选择、查询方法,装置及*** |
CN201680083959.3A CN108885606A (zh) | 2016-03-31 | 2016-03-31 | 服务节点选择、查询方法,装置及*** |
US16/146,769 US20190037485A1 (en) | 2016-03-31 | 2018-09-28 | Service node selection and query method, apparatus, and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2016/078220 WO2017166252A1 (zh) | 2016-03-31 | 2016-03-31 | 服务节点选择、查询方法,装置及*** |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/146,769 Continuation US20190037485A1 (en) | 2016-03-31 | 2018-09-28 | Service node selection and query method, apparatus, and system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017166252A1 true WO2017166252A1 (zh) | 2017-10-05 |
Family
ID=59962456
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2016/078220 WO2017166252A1 (zh) | 2016-03-31 | 2016-03-31 | 服务节点选择、查询方法,装置及*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US20190037485A1 (zh) |
EP (1) | EP3432151A4 (zh) |
CN (1) | CN108885606A (zh) |
WO (1) | WO2017166252A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20180128051A (ko) * | 2016-04-01 | 2018-11-30 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 액세스 방법, 장치, 디바이스 및 시스템 |
US11076321B2 (en) | 2018-10-11 | 2021-07-27 | Cisco Technology, Inc. | Selecting 5G non-standalone architecture capable MME during registration and handover |
US11290951B2 (en) | 2019-02-12 | 2022-03-29 | Cisco Technology, Inc. | Providing optimal packet data network gateway selection for 5G network environments upon initial user equipment attachment via a WiFi evolved packet data gateway |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10764394B2 (en) * | 2016-11-30 | 2020-09-01 | At&T Intellectual Property I, L.P. | Resource based framework to support service programmability for a 5G or other next generation mobile core network |
US10834573B2 (en) | 2019-02-15 | 2020-11-10 | At&T Mobility Ii Llc | Systems, devices and methods for managing access point name information by operators and users on the SIM |
CN114157579A (zh) * | 2019-04-24 | 2022-03-08 | 华为技术有限公司 | 接入网关的方法及装置 |
CN112994923B (zh) * | 2019-12-18 | 2023-04-07 | ***通信集团浙江有限公司 | 网元选取方法及装置 |
CN114124737B (zh) * | 2020-08-25 | 2023-07-11 | 华为技术有限公司 | 一种控制用户设备接入网络的方法及装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090234956A1 (en) * | 2007-06-14 | 2009-09-17 | Huawei Technologies Co., Ltd. | Method, apparatus and system for establishing a connection |
CN101631354A (zh) * | 2008-07-18 | 2010-01-20 | 华为技术有限公司 | 一种分组数据网络选择的方法、装置与*** |
CN102238727A (zh) * | 2010-04-22 | 2011-11-09 | 大唐移动通信设备有限公司 | 一种选择分组数据网络网关pdn gw节点的方法、装置和*** |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090234695A1 (en) * | 2007-10-16 | 2009-09-17 | Kapadi Mangesh D | System and method for harvesting scheduling, planting scheduling and capacity expansion |
CN101677470B (zh) * | 2008-09-18 | 2011-12-21 | 华为技术有限公司 | 服务请求的处理方法、装置及*** |
KR101913253B1 (ko) * | 2011-02-11 | 2018-10-30 | 엘지전자 주식회사 | 이동통신 네트워크 내에서 제어 평면을 담당하는 서버 및 그 서버에서 서비스를 제어하는 방법 |
US9642077B2 (en) * | 2013-10-23 | 2017-05-02 | Cisco Technology, Inc. | Node selection in virtual evolved packet core |
US9730056B2 (en) * | 2015-08-14 | 2017-08-08 | Telefonaktiebolaget Lm Ericsson (Publ) | System, method, and apparatus for facilitating selection of a serving node |
GB2558585A (en) * | 2017-01-06 | 2018-07-18 | Nec Corp | Communication system |
-
2016
- 2016-03-31 CN CN201680083959.3A patent/CN108885606A/zh active Pending
- 2016-03-31 EP EP16896032.6A patent/EP3432151A4/en not_active Withdrawn
- 2016-03-31 WO PCT/CN2016/078220 patent/WO2017166252A1/zh active Application Filing
-
2018
- 2018-09-28 US US16/146,769 patent/US20190037485A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090234956A1 (en) * | 2007-06-14 | 2009-09-17 | Huawei Technologies Co., Ltd. | Method, apparatus and system for establishing a connection |
CN101631354A (zh) * | 2008-07-18 | 2010-01-20 | 华为技术有限公司 | 一种分组数据网络选择的方法、装置与*** |
CN102238727A (zh) * | 2010-04-22 | 2011-11-09 | 大唐移动通信设备有限公司 | 一种选择分组数据网络网关pdn gw节点的方法、装置和*** |
Non-Patent Citations (4)
Title |
---|
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Enhancements of D edicated Core Networks selection; mechanism; (Release 14", 3GPP TR 23.711, 31 January 2016 (2016-01-31), XP055426684 * |
HUAWEI ET AL.: "DCN serving node overload control based on the congestion level", 3GPP TSG SA WG2 MEETING #113, 29 January 2016 (2016-01-29), pages 1 - 3, XP051072186 * |
NEC: "Dedicated Core Network (DCN) selection based on UE' s indication to RAN", SA WG2 MEETING #111, 23 October 2015 (2015-10-23), XP051035145 * |
See also references of EP3432151A4 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20180128051A (ko) * | 2016-04-01 | 2018-11-30 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 액세스 방법, 장치, 디바이스 및 시스템 |
KR102166741B1 (ko) | 2016-04-01 | 2020-10-16 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 액세스 방법, 장치, 디바이스 및 시스템 |
US10863555B2 (en) | 2016-04-01 | 2020-12-08 | Huawei Technologies Co., Ltd. | Access method, apparatus, device, and system |
US11076321B2 (en) | 2018-10-11 | 2021-07-27 | Cisco Technology, Inc. | Selecting 5G non-standalone architecture capable MME during registration and handover |
US11290951B2 (en) | 2019-02-12 | 2022-03-29 | Cisco Technology, Inc. | Providing optimal packet data network gateway selection for 5G network environments upon initial user equipment attachment via a WiFi evolved packet data gateway |
Also Published As
Publication number | Publication date |
---|---|
EP3432151A4 (en) | 2019-04-03 |
CN108885606A (zh) | 2018-11-23 |
EP3432151A1 (en) | 2019-01-23 |
US20190037485A1 (en) | 2019-01-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017166252A1 (zh) | 服务节点选择、查询方法,装置及*** | |
US11259240B2 (en) | Selecting a network slice identifier | |
US10638308B2 (en) | Network slice management apparatus and network slice management method | |
WO2018006784A1 (zh) | 一种网络切片选择方法、设备及*** | |
JP5323861B2 (ja) | ネットワーク・リソースをプールするための方法および装置 | |
WO2017012402A1 (zh) | 一种网络切片的选择方法及*** | |
WO2018161803A1 (zh) | 一种网络切片的选择方法及装置 | |
WO2019141120A1 (zh) | 一种pcf寻址方法及装置、设备、存储介质 | |
WO2015184722A1 (zh) | 专用网络选择方法及装置 | |
JP2020516165A (ja) | セッション管理機能選択のための方法および装置 | |
US11750708B2 (en) | Method and device for proxy between different architectures | |
JP2022116193A (ja) | 通信方法、通信装置、および通信システム | |
CN107645722B (zh) | 专用网络选择接入方法和***、公网mme、hss和基站 | |
EP3485665A1 (en) | Access control in communications network comprising slices | |
US11456989B2 (en) | Systems and methods for virtualized network function (“VNF”) selection in a wireless telecommunications network | |
RU2661680C2 (ru) | Способ, устройство и система обработки передаваемых данных | |
WO2019076292A1 (zh) | 管理方法及装置、网关控制面网元、通信***及存储介质 | |
WO2022052875A1 (zh) | 终端跨区域通信方法、网元设备及存储介质 | |
WO2016000172A1 (zh) | 网络设备及分配接入点名称的方法 | |
EP3845001B1 (en) | Traffic in a distributed cloud system | |
JP6610908B2 (ja) | 通信システム | |
EP4113943A1 (en) | System and method for subscriber awareness in a 5g network | |
WO2017206921A1 (zh) | 一种子网接入方法、装置及计算机可读存储介质 | |
WO2022141528A1 (zh) | 一种确定mec接入点的方法及装置 | |
WO2017049919A1 (zh) | 用户签约数据获取方法、s4sgsn设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2016896032 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2016896032 Country of ref document: EP Effective date: 20181015 |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16896032 Country of ref document: EP Kind code of ref document: A1 |