WO2018077023A1 - 支持non-3GPP接入的用户面功能实体选择方法、设备及系统 - Google Patents

支持non-3GPP接入的用户面功能实体选择方法、设备及系统 Download PDF

Info

Publication number
WO2018077023A1
WO2018077023A1 PCT/CN2017/105363 CN2017105363W WO2018077023A1 WO 2018077023 A1 WO2018077023 A1 WO 2018077023A1 CN 2017105363 W CN2017105363 W CN 2017105363W WO 2018077023 A1 WO2018077023 A1 WO 2018077023A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
entity
function entity
3gpp
functional entity
Prior art date
Application number
PCT/CN2017/105363
Other languages
English (en)
French (fr)
Inventor
于游洋
孙晓姬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP17864628.7A priority Critical patent/EP3503624B1/en
Publication of WO2018077023A1 publication Critical patent/WO2018077023A1/zh
Priority to US16/382,746 priority patent/US10952114B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H04W36/00226—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB] wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a user plane (UP) functional entity selection method, device and system supporting non-3rd generation partnership project (non-3GPP) access.
  • UP user plane
  • non-3GPP non-3rd generation partnership project
  • the 3GPP standards group developed the next-generation mobile system (next generation system) network architecture at the end of 2016, called the 5th generation (5th generation, 5G) network architecture.
  • the architecture not only supports the wireless technology defined by the 3GPP standard group to access the 5G core network, but also supports the non-3GPP access technology to access the 5G core network.
  • the core network functions of the 5G core network are divided into UP function and control plane (CP) function.
  • the UP function entity is mainly responsible for packet data packet forwarding, quality of service (QoS) control, and accounting information statistics.
  • the CP function entity is responsible for delivering data packet forwarding policies and QoS control policies to the UP.
  • the CP function entity selects a suitable UP function entity for the UE, and the UP function entity establishes a user plane connection with the wireless side, and provides the UE with the UE side.
  • suitable UP function entity refers to an UP function entity that has a low current load and can support an access point name (APN).
  • the previously selected UP functional entity may no longer be suitable to continue to serve the UE, thereby failing to guarantee continuity of the service.
  • the embodiment of the present invention provides a user plane function entity selection method, device, and system for supporting non-3GPP access, so as to at least solve the current UP function entity selected when the UE moves from the 3GPP network to the non-3GPP network. It is no longer suitable to continue to serve the UE, so there is no guarantee of continuity of the business.
  • the embodiment of the present invention provides the following technical solutions:
  • a method for selecting an UP function entity that supports non-3GPP access includes: when a UE accesses from a 3GPP network, the CP function entity acquires subscription data of the UE, where the subscription data includes Whether the UE is allowed to access the indication information of the non-3GPP network; if the indication information indicates that the UE is allowed to access the non-3GPP network, the CP function entity selects the target UP function entity supporting the non-3GPP access.
  • the CP functional entity is choosing to support When the target UP functional entity accessing the non-3GPP, considering whether the UE is allowed to access the non-3GPP network, the CP functional entity selects to support the non-3GPP access in the case of allowing the UE to access the non-3GPP network.
  • Target UP functional entity Since the interface NG3 shown in FIG. 1 exists between the target UP function entity supporting the non-3GPP access and the non-3GPP access gateway, when the UE moves from the 3GPP network to the non-3GPP network access, the The target UP functional entity is still suitable to continue to serve the UE, thereby ensuring continuity of the service.
  • the CP function entity selects a target UP function entity that supports non-3GPP access, including: the CP function entity acquires non-3GPP access capability of at least one UP function entity; The non-3GPP access capability of the at least one UP functional entity selects a target UP functional entity supporting non-3GPP access from the at least one UP functional entity. That is, the CP functional entity may select a target UP functional entity supporting non-3GPP access based on the subscription data and the non-3GPP access capability of the UP functional entity.
  • the subscription data includes indication information about whether the UE is allowed to access the non-3GPP network
  • the method includes: the subscription data includes a network access mode parameter, where the network access mode parameter is set. For the packet switched domain, or if the network access mode parameter is set to a packet switched domain or a voice service domain, it indicates that the UE is allowed to access the non-3GPP network; if the network access mode parameter is set to the voice service domain, The UE is not allowed to access the non-3GPP network; or if the subscription data includes the non-3GPP permission indication, the UE is allowed to access the non-3GPP network; if the subscription data does not include the non-3GPP permission indication, The UE is not allowed to access the non-3GPP network; or if the subscription data includes the non-3GPP disallow indication, the UE is not allowed to access the non-3GPP network, and if the subscription data does not include non- The 3GPP does not allow indication, which means that the UE is allowed to access the non-3GPP
  • the non-3GPP access capability of the at least one UP functional entity includes: an UP functional entity supporting a network protocol secure connection IPSec, an interface between the UP functional entity supporting the non-3GPP access gateway, and an UP.
  • the functional entity is fused with the non-3GPP access gateway, or the UP functional entity supports at least one of the point-to-point protocol PPPOE on the Ethernet.
  • the CP function entity acquires the non-3GPP access capability of the at least one UP function entity, including: the CP function entity acquires the non-3GPP access capability of the at least one UP function entity by using the domain name system DNS query. Or the CP function entity acquires the non-3GPP access capability of the configured at least one UP function entity, wherein the CP function is established when each of the at least one UP function entity establishes a connection with the CP function entity The entity receives the connection establishment request message sent by each UP function entity, where the connection establishment request message carries the non-3GPP access capability of each UP function entity. That is to say, the CP functional entity can acquire the non-3GPP access capability of at least one UP functional entity in the above manner.
  • the method further includes: the CP functional entity acquiring the non-3GPP access capability of the UE; the CP functional entity selecting, according to the non-3GPP access capability of the at least one UP functional entity, the non-3GPP from the at least one UP functional entity
  • the target UP function entity of the access includes: if the UE's non-3GPP access capability indicates that the UE is a UE supporting non-3GPP access, the CP function entity is based on the non-3GPP access of the at least one UP function entity
  • the capability selects a target UP functional entity supporting non-3GPP access from the at least one UP functional entity.
  • the CP functional entity selects the target UP functional entity supporting the non-3GPP access, it not only considers whether the UE is allowed to access the non-3GPP network, but also considers the non-3GPP access capability of the UE. In the case that the UE is allowed to access the non-3GPP network, if the non-3GPP access capability of the UE indicates that the UE is a UE supporting non-3GPP access, the CP functional entity is based on the non-3GPP access capability of the UP functional entity. Choose A target UP functional entity supporting non-3GPP access.
  • the non-3GPP access capability of the UE includes: the UE supports multiple access, the UE supports wireless fidelity Wifi access, the UE supports IPSec, and the UE supports fixed network access. At least one of the capability, the UE's ability to support access to the unlicensed spectrum, or the UE's ability to support PPPOE.
  • the method further includes: when the UE accesses from the non-3GPP network, the CP function entity receives the a non-access stratum NAS signaling sent by the UE, where the NAS signaling carries a packet data unit PDU session establishment request message; the CP function entity sends the PDU session establishment request message to the target UP function entity; the CP function entity receives the The PDU session setup response message sent by the target UP function entity, the PDU session setup response message carrying the full tunnel endpoint identifier F-TEID of the target UP function entity allocated by the target UP function entity, and the F-TEID of the target UP function entity includes The network protocol IP address of the target UP function entity and the tunnel end point identifier TEID of the target UP function entity; the CP function entity sends the F-TEID of the target UP function entity to the non-3GPP access gateway N3G-GW;
  • the target UP function entity can learn the F-TEID of the N3G-GW, and the N3G-GW can know the F-TEID of the target UP function entity, so that the session connection between the N3G-GW and the target UP can be established.
  • the IP address of the target UP functional entity and the IP address of the N3G-GW are IP addresses of the device granularity
  • the TEID of the target UP functional entity and the TEID of the N3G-GW are device granularity.
  • TEID; or, the IP address of the target UP function entity and the IP address of the N3G-GW are the IP address of the session granularity
  • the TEID of the target UP function entity and the TEID of the N3G-GW are the TEID of the session granularity.
  • the F-TEID in the application of the present invention may be not only the F-TEID of the device granularity but also the F-TEID of the session granularity.
  • the method further includes: the CP function entity is based on the location of the UE And at least one condition of whether the N3G-GW is integrated with the target UP functional entity or the load condition of the N3G-GW, etc., that the UE selects the target N3G-GW; the CP functional entity sends the identifier of the target N3G-GW to the UE. .
  • the target N3G-GW is selected for the UE based on at least one condition such as the location of the UE, whether the N3G-GW is integrated with the target UP functional entity, or the load condition of the N3G-GW. So that the N3G-GW with a lower load closer to the UE can be obtained.
  • the method further includes: the CP function entity sending the UE to the UE An identifier of the target UP functional entity, the identifier of the target UP functional entity being used by the UE to select a target N3G-GW that is unified with the target UP functional entity or is closest to the physical location of the target UP functional entity.
  • the target N3G-GW is selected for the UE based on at least one condition such as the location of the UE, whether the N3G-GW is integrated with the target UP functional entity, or the load condition of the N3G-GW. So that the N3G-GW with a lower load closer to the UE can be obtained.
  • the method further includes: when the UE accesses from the non-3GPP network, the CP function entity is based on the At least one condition of the location of the UE, or whether the N3G-GW is unified with the target UP functional entity, or the N3G-GW load condition, is that the UE selects the target N3G-GW; the initial N3G that the CP functional entity accesses through the UE The GW sends the identity of the target N3G-GW to the UE.
  • the CP function entity may also perform N3G-GW reselection and notify the UE of the reselected target N3G-GW identifier.
  • the UE disconnects from the previous N3G-GW and initiates an IPSec establishment procedure to the target N3G-GW. among them,
  • the reselected target N3G-GW is selected based on at least one condition such as the location of the UE, or whether the N3G-GW is integrated with the target UP functional entity, or the load condition of the N3G-GW, so that the load closer to the UE can be acquired.
  • the lower N3G-GW that is, the UE can establish an IPsec connection with the lower load N3G-GW that is closer to the UE.
  • an embodiment of the present invention provides a CP function entity, which has a function of implementing the behavior of a CP function entity in the foregoing method embodiment.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • an embodiment of the present invention provides a CP functional entity, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when When the CP functional entity is running, the processor executes the computer-executed instructions stored by the memory to cause the CP functional entity to perform the UP-3 physical entity selection method of the non-3GPP access according to any of the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the CP functional entity, including a program designed to perform the foregoing aspects for a CP functional entity.
  • FIG. 1 is a schematic diagram of a 5G network architecture according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for selecting an UP functional entity for non-3GPP access according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of another method for selecting an UP functional entity for non-3GPP access according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a method for selecting an UP functional entity for non-3GPP access according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of a method for selecting an UP functional entity for non-3GPP access according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of a method for selecting an UP functional entity for non-3GPP access according to an embodiment of the present disclosure
  • FIG. 8 is a schematic structural diagram of a CP functional entity according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of another CP function entity according to an embodiment of the present invention.
  • FIG. 1 it is a 5G network architecture provided by an embodiment of the present invention.
  • the architecture not only supports the wireless technology defined by the 3GPP standard group to access the 5G core network, but also supports the non-3GPP access technology to access the 5G core network.
  • the access point accesses the 5G core network through a radio access network (RAN) access point.
  • the RAN access point communicates with the CP functional entity of the 5G core network through the next generation network interface (NG) 2, and communicates with the UP functional entity of the 5G core network through the NG3;
  • the 5G core network is accessed through a non-3GPP access gateway (N-3G-GW).
  • the N3G-GW includes an N3G-GW control plane (N3G-GW-C) and an N3G-GW user plane (N3G-GW-U).
  • the N3G-GW-C communicates with the CP functional entity of the 5G core network through the NG2, N3G-GW.
  • -U communicates with the UP functional entity of the 5G core network through NG3.
  • the CP function entity communicates with the application function (AF) entity of the 5G core network through the NG5, and sends a packet forwarding policy, a QoS control policy, and the like to the UP function entity through the NG4; the UP function entity passes the NG6. It communicates with the data network (DN) entity of the 5G core network, and is responsible for packet data packet forwarding, QoS control, and accounting information statistics.
  • AF application function
  • DN data network
  • the above 5G network architecture may further include a home subscriber server (HSS) for supporting an internet protocol (IP) multimedia subsystem (IP multimedia subsystem) for processing or invoking a session.
  • HSS home subscriber server
  • IP multimedia subsystem IP multimedia subsystem
  • IMS internet protocol multimedia subsystem
  • the functions provided by the HSS include IP multimedia functions, home location register (HLR) functions necessary for the packet switched (PS) domain, and HLR functions required for the call service (CS) domain.
  • HLR home location register
  • PS packet switched
  • CS call service
  • the information that the HSS can process includes user identification, number and address information; user security information, that is, network access control information for authentication and authorization; user location information, that is, HSS supports user registration, storage location information, user list information, and the like.
  • the HSS is mainly used to provide the subscription data of the UE when the UE accesses from the 3GPP network, so that the CP function entity determines whether to allow the UE to access the non-3GPP network according to the subscription data.
  • 5G network architecture may also include other modules or network entities, which are not specifically limited in this embodiment of the present invention.
  • the UE involved in the present application may include various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of UEs.
  • Mobile station (MS) mobile station
  • terminal terminal equipment
  • soft terminal soft terminal
  • the devices mentioned above are collectively referred to as user equipments or UEs.
  • CP functional entity and "UP functional entity” are only one name, and the name itself does not limit the device.
  • the "CP functional entity” may also be replaced by "CP function”, and the "UP functional entity” may also be replaced with “UP function”; or, the "CP functional entity” may be replaced with “CP”, the “UP functional entity” may also be replaced with "UP”, etc., which are uniformly described herein, and will not be described below.
  • any one of the above-mentioned 5G network architectures may be implemented by one physical device or multiple physical devices;
  • the functional nodes or network elements, such as the CP functional entity and the UP functional entity may be implemented by different physical devices, or may be implemented by the same physical device, which is not specifically limited in this embodiment of the present invention. That is, it can be understood that any one of the above-mentioned 5G network architectures, such as a CP function entity or an UP function entity, may be a logical function module or a plurality of entities in the entity device.
  • a logical function module of the device is not specifically limited in this embodiment of the present invention.
  • the CP functional entity in FIG. 1 can be implemented by the computer device (or system) in FIG. 2.
  • FIG. 2 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • the computer device 200 includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.
  • the processor 201 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of the present invention. integrated circuit.
  • CPU general purpose central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 202 can include a path for communicating information between the components described above.
  • the communication interface 204 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 203 is used to store application code for executing the solution of the present invention, and is controlled by the processor 201 for execution.
  • the processor 201 is configured to execute application code stored in the memory 203 to implement UP functional entity selection of non-3GPP access.
  • processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 200 can include multiple processors, such as processor 201 and processor 208 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 200 may also include an output device 205 and an input device 206.
  • Output device 205 is in communication with processor 201 and can display information in a variety of ways.
  • the output device 205 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.
  • Input device 206 is in communication with processor 201 and can accept user input in a variety of ways.
  • input device 206 can be a mouse, keyboard, touch screen device or sensing device, and the like.
  • the computer device 200 described above can be a general purpose computer device or a special purpose computer device.
  • the computer device 200 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or have FIG. A device of similar structure.
  • Embodiments of the invention do not limit the type of computer device 200.
  • FIG. 3 is a schematic flowchart of a method for selecting an UP functional entity for non-3GPP access according to an embodiment of the present invention.
  • the following is an example of the UE accessing from the 3GPP network in the 5G network architecture shown in FIG. 1 , which involves the interaction between the UE, the RAN access point, the UP functional entity, the CP functional entity, and the HSS, including the following.
  • Steps S301-S310
  • the UE establishes a connection with the RAN access point, and sends an attach request message to the CP function entity by using the RAN access point, so that the CP function entity receives the attach request message.
  • the attach request message includes a UE identifier, such as a UE temporary identifier or a UE permanent identifier.
  • a UE permanent identifier may be an international mobile subscriber identification number (IMSI).
  • the attach request message may further include at least one of a non-3GPP access capability of the UE, or a type indication of the connection.
  • the above non-3GPP access capabilities include:
  • the UE supports multiple access, the UE supports wireless-fidelity (WiFi) access, the UE supports IP security connection (IPSec), the UE supports fixed network access, and the UE supports unlicensed spectrum access. Or the UE supports at least one of a point-to-point protocol over ethernet (PPPOE).
  • WiFi wireless-fidelity
  • IPSec IP security connection
  • PPOE point-to-point protocol over ethernet
  • connection type indications include:
  • the UE will subsequently initiate a non-3GPP access indication, or the connection is at least one of a multi-connection indication.
  • the CP functional entity sends a subscription data request to the HSS, so that the HSS receives the subscription data request.
  • the subscription data request may be a subscription data acquisition message or a update location request message, which is not specifically limited in this embodiment of the present invention.
  • the above message contains the UE permanent identity.
  • the UE permanent identifier may be obtained by using the attach request message in step S301, or may be obtained according to the UE temporary identifier carried in the attach request message in step S301, which is not specifically limited in this embodiment of the present invention.
  • the identifier of the CP function entity may be carried in the foregoing message, which is not specifically limited in this embodiment of the present invention.
  • the HSS acquires subscription data of the UE according to the permanent identifier of the UE, where the subscription data includes indication information about whether the UE is allowed to access the non-3GPP network.
  • the embodiment of the present invention does not specifically limit the manner in which the UE is allowed to access the non-3GPP network in the subscription data.
  • the following three solutions are provided by way of example:
  • the subscription data includes a network access mode parameter, wherein if the network access mode parameter is set to a PS domain, or if the network access mode parameter is set to PS domain or CS
  • the domain indicates that the UE is allowed to access the non-3GPP network. If the network access mode parameter is set to the CS domain, the UE is not allowed to access the non-3GPP network.
  • Solution 2 If the non-3GPP allowed indication is included in the subscription data, the UE is allowed to access the non-3GPP network; if the subscription data does not include the non-3GPP permission indication, the UE is not allowed to access. non-3GPP network.
  • Solution 3 If the non-3GPP not allowed indication is included in the subscription data, the UE is not allowed to access the non-3GPP network; if the subscription data does not include the non-3GPP disallow indication, the permission is allowed. The UE accesses the non-3GPP network.
  • non-3GPP permission indication may also be replaced by a non-3GPP authorized indication, which is not specifically limited in this embodiment of the present invention.
  • the HSS sends a subscription data response to the CP function entity, so that the CP function entity receives the subscription data response.
  • the subscription data response here Specifically, it may be a subscription data response message; if the subscription data request in step S302 is specifically an update location request (update location request) message, the subscription data response here may specifically be an update location response message, and the present invention The embodiment does not specifically limit this.
  • the above message includes the subscription data.
  • the CP function entity selects a target UP function entity that supports non-3GPP access based on the subscription data.
  • the indication information included in the subscription data whether the UE is allowed to access the non-3GPP network indicates that the UE is allowed to access the non-3GPP network, or the indication information included in the subscription data whether the UE is allowed to access the non-3GPP network is included. Instructing to allow the UE to access the non-3GPP network, and satisfying at least one condition, that is, for a UE supporting non-3GPP access, or for a UE or multiple access packet data unit that will subsequently initiate non-3GPP access ( A packet data unit (PDU) connection, the CP function entity selects a target UP function entity supporting non-3GPP access from at least one UP function entity.
  • PDU packet data unit
  • the CP function entity selects the target UP function entity that supports the non-3GPP access
  • at least one of the non-3GPP access capability of the UP function entity or the user plane type supported by the UP function entity is also considered.
  • the non-3GPP access capability of the foregoing UP functional entity includes:
  • the UP functional entity supports at least one of IPSec, an interface between the UP functional entity and the non-3GPP access gateway, an UP functional entity and a non-3GPP access gateway, or an UP functional entity supporting the PPPOE.
  • the user plane types supported by the above UP functional entities include:
  • the embodiment of the present invention does not specifically limit the manner in which the CP function entity acquires at least one of the non-3GPP access capability of the UP function entity or the user plane type supported by the UP function entity, and provides the following two solutions:
  • Solution 1 When the UP function entity establishes a connection with the CP function entity, at least one of the non-3GPP access capability of the UP function entity or the user plane type supported by the UP function entity is reported. For example, the UP function entity sends an Sx Setup request message to the CP function entity, where the message includes at least one of a non-3GPP access capability of the UP function entity or a user plane type supported by the UP function entity.
  • the CP functional entity queries the domain name system (DNS) to obtain the non-3GPP access capability of the UP functional entity.
  • DNS domain name system
  • the DNS system sends the interface information supported by the UP function entity to the CP function entity, and the interface information includes an interface with the non-3GPP access gateway, such as NG3 in FIG.
  • the DNS sends the user plane type supported by the UP function entity to the CP function entity.
  • the CP function entity selects the target UP function entity that supports the non-3GPP access
  • the current load condition of the UP function entity, whether the UP function entity supports the related APN, and the location information of the UP function entity may be considered. At least one embodiment of the present invention does not specifically limit this.
  • the CP function entity sends a PDU session establishment request message to the target UP function entity, so that the target UP function entity receives the PDU session establishment request message.
  • the target UP function entity allocates a fully qualified tunnel endpoint identifier (F-TEID) of the target UP function entity to the PDU connection on the 3GPP side, and is denoted as F-TEID1, where the F-TEID1 includes the target UP function entity.
  • F-TEID1 includes the target UP function entity.
  • the above-mentioned F-TEID1 is used to search for the user context, that is, the specific processing board (the board corresponding to the TEID) of the specific device (the device corresponding to the IP address) where the user context information is located.
  • the F-TEID1 can be the F-TEID of the device granularity, that is, the IP address of the target UP functional entity is the IP address of the device granularity, and the TEID of the target UP functional entity is the TEID of the device granularity; the F-TEID1 can also be the session granularity.
  • the IP address is the IP address of the session granularity
  • the TEID of the target UP functional entity is the TEID of the session granularity, which is not specifically limited in this embodiment of the present invention.
  • the F-TEID of the target UP function entity allocated by the target UP function entity to the PDU connection on the 3GPP side is denoted as F-TEID1, and is used to connect to the PDU of the non-3GPP side of the following target UP function entity.
  • the F-TEID of the assigned target UP functional entity is distinguished, and is described here in a unified manner. The description is applicable to the following embodiments, and details are not described herein.
  • the target UP function entity sends a PDU session establishment response message to the CP function entity, where the PDU session establishment response carries the F-TEID1, so that the CP function entity receives the PDU session establishment response message.
  • the CP function entity stores the correspondence between the F-TEID1 and the UE, so that the UE acquires the F-TEID1 according to the corresponding relationship in a subsequent 3GPP session or other 3GPP processes.
  • the CP function entity sends an attach response message to the UE by using the RAN access point, so that the UE receives the attach response message.
  • the CP functional entity selects a target UP functional entity supporting non-3GPP access, considering factors of whether to allow the UE to access the non-3GPP network, in the case of allowing the UE to access the non-3GPP network, the CP The functional entity selects a target UP functional entity that supports non-3GPP access. Since the interface NG3 shown in FIG. 1 exists between the target UP function entity supporting the non-3GPP access and the non-3GPP access gateway, when the UE moves from the 3GPP network to the non-3GPP network access, the The target UP functional entity is still suitable to continue to serve the UE, thereby ensuring continuity of the service.
  • the actions of the CP function entities in the foregoing S302, S305, S306, S309, and S310 can be performed by the processor 201 in the computer device 200 shown in FIG. 2 by calling the application code stored in the memory 203, which is performed by the embodiment of the present invention. This is not subject to any restrictions.
  • the UE may also initiate a non-3GPP access and PDU session establishment process from the 5G network architecture shown in FIG. 1, involving the UE, the N3G access point, the N3G-GW, and the UP function.
  • the interaction between the entity and the CP functional entity, the UP functional entity in the process is the target UP functional entity selected in the case of the foregoing 3GPP access, and the process includes the following steps S311-S321:
  • S311 The UE establishes a connection with the N3G-GW, and obtains an IP address of the N3G-GW or the N3G-GW, and then establishes an IPSec with the N3G-GW.
  • the N3G access point may be, for example, a WiFi access point (AP) or a WiFi access controller (Access Control, AC).
  • AP WiFi access point
  • AC Access Control
  • the N3G-GW identifier or the IP address of the N3G-GW can be obtained through a DNS query.
  • the UE may establish an IPSec with the N3G-GW.
  • the UE may send an IKEv2 message to the N3G-GW through the N3G access point, where the IKEv2 message may be an internet key exchange_authentication IKE_AUTH message.
  • the IKE_AUTH message may carry non-access stratum (NAS) signaling or an extensible authentication protocol (EAP) signaling, which is not specifically limited in this embodiment of the present invention.
  • NAS non-access stratum
  • EAP extensible authentication protocol
  • the N3G-GW acquires the NAS signaling in step S311, and sends NAS signaling to the CP functional entity by using an interface NG2 message with the CP functional entity as shown in FIG. 1 to enable the CP functional entity to receive the NAS signaling. make.
  • the NAS signaling may include, for example, a PDU session establishment request message.
  • the CP function entity parses the NAS signaling, obtains a PDU session establishment request message, and sends a PDU session establishment request message to the target UP function entity, so that the target UP function entity receives the PDU session establishment request message.
  • the target UP function entity is an UP function entity selected in the case that the UE accesses from the 3GPP network in the foregoing embodiment.
  • the correspondence between the identifier of the UP function entity and the APN corresponding to the UP function entity may be previously stored in the CP function entity.
  • the target UP function entity allocates the F-TEID of the target UP function entity to the PDU connection on the non-3GPP side, and records it as F-TEID2.
  • the F-TEID2 includes the IP address of the target UP functional entity and the TEID of the target UP functional entity.
  • the F-TEID2 is used to search for the user context, that is, the specific processing board (the board corresponding to the TEID) of the specific device (the device corresponding to the IP address) where the user context information is located.
  • the F-TEID2 can be the F-TEID of the device granularity, that is, the IP address of the target UP functional entity is the IP address of the device granularity, and the TEID of the target UP functional entity is the TEID of the device granularity; the F-TEID2 can also be the session granularity.
  • the F-TEID that is, the IP address of the target UP function entity is the IP address of the session granularity
  • the TEID of the target UP function entity is the TEID of the session granularity, which is not specifically limited in this embodiment of the present invention.
  • the F-TEID of the target UP function entity allocated by the target UP function entity for the PDU connection on the non-3GPP side is denoted as F-TEID2, and is used to allocate the PDU connection with the target UP function entity on the 3GPP side.
  • the F-TEID of the target UP functional entity is distinguished, and is described here in a unified manner. The description is applicable to the following embodiments, and details are not described herein again.
  • the F-TEID1 and the F-TEID2 in the embodiment of the present invention may be the same or different.
  • the embodiment of the present invention does not specifically limit this.
  • the target UP function entity sends a PDU session establishment response message to the CP function entity, where the PDU session establishment response carries the F-TEID2, so that the CP function entity receives the PDU session establishment response message.
  • the CP functional entity sends the F-TEID2 to the N3G-GW through the NG2 interface message as shown in FIG.
  • the above NG2 interface message is a connection establishment request message, an NG2 message, or the like.
  • the CP function entity may also send the NAS signaling sent to the UE to the N3G-GW through an interface NG2 message with the N3G-GW as shown in FIG. 1.
  • the NAS signaling may include, for example, a PDU session establishment response message.
  • the N3G-GW stores the correspondence between the F-TEID2 and the UE, where the UE acquires the F-TEID2 according to the correspondence in a subsequent non-3GPP session or other non-3GPP processes. At the same time, the N3G-GW allocates the F-TEID of the N3G-GW, and the F-TEID of the N3G-GW includes the IP address of the N3G-GW and the TEID of the N3G-GW.
  • the F-TEID of the N3G-GW is used to search for the user context, that is, the specific processing board (the board corresponding to the TEID) of the specific device (the device corresponding to the IP address) where the user context information is located.
  • the F-TEID of the N3G-GW may be the F-TEID of the device granularity, that is, the IP address of the N3G-GW is the IP address of the device granularity, and the TEID of the N3G-GW is the TEID of the device granularity; the N3G-GW
  • the F-TEID may also be the F-TEID of the session granularity, that is, the IP address of the N3G-GW is the IP address of the session granularity, and the TEID of the N3G-GW is the TEID of the session granularity, which is not specifically limited in this embodiment of the present invention. .
  • the N3G-GW sends the F-TEID of the N3G-GW to the CP function entity by using the NG2 interface message as shown in FIG.
  • the CP functional entity is caused to receive the F-TEID of the N3G-GW.
  • the NG2 interface message may be, for example, a connection setup response message, an NG2 message, or the like.
  • the CP function entity sends a PDU session modification request message to the target UP function entity, where the PDU session update request message carries the F-TEID of the N3G-GW, so that the target UP function entity receives the PDU session update request. Message.
  • the target UP function entity may store the mapping between the F-TEID of the N3G-GW and the UE for use in the subsequent non-3GPP session or other non-3GPP processes.
  • the F-TEID of the N3G-GW is obtained according to the corresponding relationship, which is not specifically limited in this embodiment of the present invention.
  • the target UP function entity can learn the F-TEID of the N3G-GW, and the N3G-GW can know the F-TEID2 of the target UP function entity, so that the session between the N3G-GW and the target UP can be established. connection.
  • the target UP function entity sends a PDU session modification response message to the CP function entity, so that the CP function entity receives the PDU session update response message.
  • the N3G-GW sends the NAS signaling sent by the CP function entity received in step S316 to the UE by using an IKEv2 message, so that the UE receives the IKEv2 message.
  • the N3G-GW encapsulates the NAS signaling in an IKEv2 message and sends it to the UE.
  • step S317 may be performed first, and then step S321 may be performed; step S321 may be performed first, and then step S317 may be performed; Step S317 and step S321 are performed at the same time, which is not specifically limited in the embodiment of the present invention.
  • the UP function entity in the foregoing process is the target UP function entity selected in the case of the foregoing 3GPP access, and in the case of the foregoing 3GPP access, when the CP function entity selects the target UP function entity supporting the non-3GPP access, Considering whether or not the UE is allowed to access the non-3GPP network, the CP function entity selects a target UP functional entity supporting non-3GPP access in case the UE is allowed to access the non-3GPP network. Considering that the interface NG3 as shown in FIG.
  • the target UP functional entity is still suitable for continuing to serve the UE, thereby ensuring continuity of the service.
  • the action of the CP function entity in the foregoing S313, S316, and S319 can be performed by the processor 201 in the computer device 200 shown in FIG. 2 by calling the application code stored in the memory 203, and the embodiment of the present invention does not impose any restriction on this. .
  • FIG. 4 it is a schematic flowchart of another non-3GPP access UP function entity selection method according to an embodiment of the present invention.
  • the following is an example of the UE accessing from the 3GPP network in the 5G network architecture shown in FIG. 1 , which involves the interaction between the UE, the RAN access point, the UP functional entity, the CP functional entity, and the HSS, including the following. Steps S401-S412:
  • the UE sends a PDU session establishment request message to the CP function entity by using the RAN access point, so that the CP function entity receives the PDU session establishment request message.
  • the PDU session establishment request message may carry at least one of the non-3GPP access capability of the UE, or the type indication of the connection.
  • the CP function entity sends a PDU session establishment response message to the UE through the RAN access point, so that the CP function entity receives the PDU session establishment response message.
  • the CP functional entity selects a target UP functional entity supporting non-3GPP access, considering factors of whether to allow the UE to access the non-3GPP network, in the case of allowing the UE to access the non-3GPP network, the CP The functional entity selects a target UP functional entity that supports non-3GPP access. Since the interface NG3 shown in FIG. 1 exists between the target UP function entity supporting the non-3GPP access and the non-3GPP access gateway, when the UE moves from the 3GPP network to the non-3GPP network access, the The target UP functional entity is still suitable to continue to serve the UE, thereby ensuring continuity of the service.
  • the UE may also initiate a non-3GPP access and PDU session establishment process from the 5G network architecture shown in FIG. 1, involving the UE, the N3G access point, the N3G-GW, and the UP function.
  • the interaction between the entity and the CP functional entity, the UP functional entity in the process is the target UP functional entity selected in the case of the foregoing 3GPP access, and the steps S413-S423 of the process are the same as the steps in the embodiment shown in FIG. S311-S321, which is not described herein again.
  • the action of the CP function entity in the foregoing S415, S418, and S421 can be performed by the processor 201 in the computer device 200 shown in FIG. 2 to call the application code stored in the memory 203, and the embodiment of the present invention does not impose any restriction on this. .
  • the CP function entity completes the selection of the target UP function entity supporting the non-3GPP access in the PDU connection establishment procedure in the case of 3GPP access
  • the CP functional entity completes the selection of the target UP functional entity supporting non-3GPP access in the attach procedure in the case of 3GPP access.
  • the UE in addition to the non-3GPP access capability of the UE, or the type indication of the connection, the UE may also carry the non-3GPP connection of the UE when the UE initiates the PDU connection establishment. At least one of the capability, or the type indication of the connection.
  • FIG. 5 a flow chart of another method for selecting a non-3GPP access UP function entity according to an embodiment of the present invention is provided.
  • the following is an example of the UE accessing from the 3GPP network in the 5G network architecture shown in FIG. 1 , which involves the interaction between the UE, the RAN access point, the UP functional entity, the CP functional entity, and the HSS, including the following.
  • the CP function entity selects the target N3G-GW for the UE based on at least one condition of the location of the UE, whether the N3G-GW is unified with the target UP function entity, or the load condition of the N3G-GW.
  • the CP function entity sends an attach response message to the UE by using the RAN access point, where the attach response message carries the target N3G-GW identifier, so that the UE receives the attach response message.
  • the target N3G-GW identifier may be, for example, a fully qualified domain name (FQDN) of the target N3G-GW, or an IP address of the target N3G-GW, in the embodiment of the present invention. This is not specifically limited.
  • FQDN fully qualified domain name
  • the CP functional entity selects a target UP functional entity supporting non-3GPP access, it considers whether the UE is allowed to access the non-3GPP network, and allows the UE to access the non-3GPP network.
  • the CP functional entity selects a target UP functional entity that supports non-3GPP access. Since the interface NG3 shown in FIG. 1 exists between the target UP function entity supporting the non-3GPP access and the non-3GPP access gateway, when the UE moves from the 3GPP network to the non-3GPP network access, the The target UP functional entity is still suitable to continue to serve the UE, thereby ensuring continuity of the service.
  • the target N3G-GW is selected for the UE based on at least one condition such as the location of the UE, whether the N3G-GW is integrated with the target UP functional entity, or the load condition of the N3G-GW. So that the N3G-GW with a lower load closer to the UE can be obtained.
  • the UE may also initiate a non-3GPP access and PDU session establishment process from the 5G network architecture shown in FIG. 1, involving the UE, the N3G access point, the target N3G-GW, and the UP.
  • the UP functional entity in the process is the target UP functional entity selected in the case of the foregoing 3GPP access
  • the N3G-GW in the process is selected in the case of the foregoing 3GPP access.
  • Target N3G-GW the process includes the following steps:
  • S512 The UE establishes a connection with the N3G access point, and initiates an IPSec connection to the target N3G-GW.
  • the UE may obtain the IP of the target N3G-GW by using a DNS query based on the received target N3G-GW identifier. The address, and in turn based on the IP address of the target N3G-GW, initiates an IPSec connection to the target N3G-GW.
  • the UE may directly initiate an IPSec connection to the target N3G-GW according to the IP address of the target N3G-GW.
  • the UE may establish an IPSec with the N3G-GW, for example, the UE may send an IKEv2 message to the N3G-GW through the N3G access point, where the IKEv2 message may be an IKE_AUTH message.
  • the IKE_AUTH message may carry the NAS signaling or the EAP signaling, which is not specifically limited in this embodiment of the present invention. The following steps in the embodiment of the present invention are described by taking the NAS signaling in the IKE_AUTH message as an example.
  • the subsequent steps in the embodiment of the present invention may refer to steps S312-S321 of FIG. 3, except that the N3G-GW of FIG. 3 is replaced by The target N3G-GW in the embodiment of the present invention is not described herein again.
  • step S510 If the target N3G-GW selected in step S510 and the target UP function entity can be combined, as shown in FIG. 5, after step S512, the following steps S513 and S514 may be further included:
  • the target N3G-GW obtains the NAS signaling in step S512, and sends NAS signaling to the CP functional entity by using an interface NG2 message with the CP functional entity as shown in FIG. 1 to enable the CP functional entity to receive the NAS. Signaling.
  • the foregoing NAS signaling may include, for example, a PDU session establishment response message.
  • the CP function entity sends NAS signaling to the UE by using an IKEv2 message, so that the UE receives the IKEv2 message.
  • the CP function entity encapsulates the NAS signaling in the IKEv2 message and sends it to the UE.
  • the UP function entity in the foregoing process is a target UP function entity selected in the case of the foregoing 3GPP access, and in the case of the foregoing 3GPP access, the CP function entity selects a target UP function that supports non-3GPP access.
  • the CP function entity selects the target UP function entity supporting the non-3GPP access in the case of allowing the UE to access the non-3GPP network.
  • the target UP functional entity is still suitable for continuing to serve the UE, thereby ensuring continuity of the service.
  • an IPsec connection is established with the target N3G-GW selected in the case of the above 3GPP access, and the target N3G-GW is based on the location of the UE, or whether the N3G-GW is
  • the N3G-GW with a lower load from the UE is selected by at least one condition, such as the one of the target UP function entities or the load condition of the N3G-GW, so that the UE can be close to the UE and has a lower load.
  • the N3G-GW establishes an IPsec connection.
  • the action of the CP function entity in the above S514 can be performed by the processor 201 in the computer device 200 shown in FIG. 2, and the application code stored in the memory 203 is called, which is not limited in this embodiment of the present invention.
  • FIG. 6 a flow chart of another method for selecting a non-3GPP access UP function entity according to an embodiment of the present invention is provided.
  • the following is an example of the UE accessing from the 3GPP network in the 5G network architecture shown in FIG. 1 , which involves the interaction between the UE, the RAN access point, the UP functional entity, the CP functional entity, and the HSS, including the following. Steps S601-S613:
  • the CP function entity selects the target N3G-GW for the UE based on at least one condition of the location of the UE, whether the N3G-GW is unified with the target UP function entity, or the load condition of the N3G-GW.
  • the CP function entity sends a PDU session establishment response message to the UE PDU through the RAN access point, where the PDU session establishment response message carries the target N3G-GW identifier, so that the CP function entity receives the PDU session establishment response message.
  • the target N3G-GW identifier may be, for example, an FQDN of the target N3G-GW or an IP address of the target N3G-GW, which is not specifically limited in this embodiment of the present invention.
  • the CP functional entity selects a target UP functional entity supporting non-3GPP access, it considers whether the UE is allowed to access the non-3GPP network, and allows the UE to access the non-3GPP network.
  • the CP functional entity selects a target UP functional entity that supports non-3GPP access. Since the interface NG3 shown in FIG. 1 exists between the target UP function entity supporting the non-3GPP access and the non-3GPP access gateway, when the UE moves from the 3GPP network to the non-3GPP network access, the The target UP functional entity is still suitable to continue to serve the UE, thereby ensuring continuity of the service.
  • the target N3G-GW is selected for the UE based on at least one condition such as the location of the UE, whether the N3G-GW is integrated with the target UP functional entity, or the load condition of the N3G-GW. So that the N3G-GW with a lower load closer to the UE can be obtained.
  • the actions of the CP function entities in the foregoing S602, S605, S607, S608, S611, S612, and S613 can be performed by the processor 201 in the computer device 200 shown in FIG. 2 calling the application code stored in the memory 203.
  • the embodiment of the invention does not impose any limitation on this.
  • the UE may also initiate a non-3GPP access and PDU session establishment process from the 5G network architecture shown in FIG. 1, involving the UE, the N3G access point, the target N3G-GW, and the UP.
  • Functional entity and CP function The interaction between the entities, the UP function entity in the process is the target UP function entity selected in the case of the above 3GPP access, and the N3G-GW in the process is the target N3G-GW selected in the case of the above 3GPP access.
  • the subsequent steps in the embodiment of the present invention may refer to steps S312-S321 of FIG.
  • step S614 of the process is replaced.
  • - S616 is the same as the steps S512-S514 in the embodiment shown in FIG. 5, and the embodiments of the present invention are not described herein again.
  • the action of the CP function entity in the above-mentioned S616 can be performed by the processor 201 in the computer device 200 shown in FIG. 2 to call the application code stored in the memory 203, which is not limited in this embodiment of the present invention.
  • the CP function entity completes the selection and target of the target UP functional entity supporting non-3GPP access in the PDU connection establishment procedure in the case of 3GPP access.
  • the selection of the N3G-GW, and in the embodiment shown in FIG. 5, the CP functional entity completes the selection of the target UP functional entity supporting the non-3GPP access and the target N3G-GW in the attach procedure in the case of 3GPP access. select.
  • the UE in addition to the non-3GPP access capability of the UE, or the type indication of the connection, the UE may also carry the non-3GPP connection of the UE when the UE initiates the PDU connection establishment. At least one of the capability, or the type indication of the connection.
  • the location of the UE may not be used by the CP function entity, or whether the N3G-GW is integrated with the target UP functional entity, or the N3G-GW.
  • At least one condition of the load condition, etc. is that the UE selects the target N3G-GW, but in an attach response message or a PDU session establishment response message sent by the CP function entity to the UE through the RAN access point.
  • the target UP function entity identifier is carried in, and the target N3G-GW is determined by the UE according to the target UP function entity identifier.
  • the method may include: after obtaining the target UP function entity identifier, the UE obtains the N3G-GW identifier list based on the DNS query N3G-GW identifier. For each N3G-GW identifier in the N3G-GW identifier list, compare the FQDN string matching degree of the FQDN of the N3G-GW corresponding to the N3G-GW identifier with the target UP functional entity identifier, preferably with the UP functional entity. The unified N3G-GW is used as the target N3G-GW. If the comparison mode is the same as the FQDN string of the two, it is a unified node.
  • the N3G-GW with the highest matching degree with the UP functional entity is selected as the target N3G-GW, and the N3G-GW is closest to the physical location of the target UP functional entity.
  • the subsequent UE initiates the non-3GPP access and PDU session establishment process from the 5G network architecture shown in FIG. 1 by referring to the embodiment shown in FIG. 5 or FIG. Narration.
  • the target N3G-GW may not be selected when the UE accesses the 3GPP network, but the target N3G-GW is selected when the UE accesses the non-3GPP network.
  • steps S701-S710 of the process of the UE accessing and establishing a PDU session from the 3GPP network in the 5G network architecture shown in FIG. 1 are the same as steps S301-S310 in the embodiment shown in FIG. Then, after step S710, the following steps may also be included:
  • the CP function entity selects the target N3G-GW for the UE based on at least one condition of the location of the UE, whether the N3G-GW is unified with the target UP function entity, or the load condition of the N3G-GW.
  • the CP function entity sends the target N3G-GW identifier to the initial N3G-GW through the NG2 interface message as shown in FIG. 1, so that the initial N3G-GW receives the target N3G-GW identifier.
  • the above NG2 interface message is a connection establishment request message, an NG2 message, or the like.
  • the CP functional entity can also send The NAS signaling sent to the UE is sent to the N3G-GW through an interface NG2 message with the N3G-GW as shown in FIG.
  • the NAS signaling may include, for example, a PDU session establishment response message.
  • the initial N3G-GW sends the NAS signaling and the target N3G-GW identifier sent by the CP function entity received in step S714 to the UE through the IKEv2 message, so that the UE receives the NAS signaling and the target N3G-GW identifier. At the same time, the initial N3G-GW disconnects from the UE.
  • the IKEv2 message may further carry a re-indication.
  • the UE initiates a connection with the target N3G-GW based on the received target N3G-GW identifier.
  • the UE may also initiate a connection with the target N3G-GW based on the redirection indication, which is not specifically limited in this embodiment of the present invention.
  • the CP function entity performs N3G-GW reselection, and the reselected target N3G-GW identifier is used. Notify the UE.
  • the UE disconnects from the previous initial N3G-GW and initiates an IPSec establishment procedure to the target N3G-GW.
  • the reselected target N3G-GW is selected based on at least one condition of the location of the UE, or whether the N3G-GW is integrated with the target UP functional entity, or the load condition of the N3G-GW, so that the UE is relatively close to the UE.
  • the N3G-GW with a lower load initiates an IPSec establishment process based on the N3G-GW that is closer to the UE and has a lower load.
  • the location of the UE may not be used by the CP function entity, or whether the N3G-GW is integrated with the target UP functional entity, or the load of the N3G-GW.
  • At least one condition is that the UE selects the target N3G-GW, but carries the target UP function entity identifier in the NG2 message sent by the CP function entity to the initial N3G-GW, and then the initial N3G-GW sends the message to the UE through the N3G access point.
  • the IKEv2 message carries the target UP function entity identifier, so that the UE determines the target N3G-GW according to the target UP function entity identifier.
  • the UE may initiate a connection with the target N3G-GW based on the target N3G-GW identifier.
  • the UE may initiate a connection with the target N3G-GW based on the target N3G-GW identifier.
  • Steps S401-S412 are not specifically limited in this embodiment of the present invention.
  • the device for implementing the CP functional entity includes a hardware structure and/or a software module corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may perform a function module division on a CP functional entity according to the foregoing method example, for example, Each function module is divided into individual functions, and two or more functions can be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 8 shows a possible structural diagram of the CP functional entity involved in the foregoing embodiment, and the CP functional entity 800 includes: an obtaining module 801 and a selection. Module 802.
  • the obtaining module 801 is configured to acquire, when the UE accesses from the 3GPP network, the subscription data of the UE, where the subscription data includes indication information about whether the UE is allowed to access the non-3GPP network.
  • the selecting module 802 is configured to select a target UP functional entity supporting non-3GPP access if the indication information indicates that the UE is allowed to access the non-3GPP network.
  • the selecting module 802 selects a target UP function entity that supports non-3GPP access, including: the selecting module 802 acquiring non-3GPP access capability of at least one UP function entity; and according to the non- The 3GPP access capability selects a target UP functional entity supporting non-3GPP access from the at least one UP functional entity.
  • the non-3GPP access capability of the at least one UP functional entity includes:
  • the UP functional entity supports at least one of IPSec, an interface between the UP functional entity and the non-3GPP access gateway, an UP functional entity and a non-3GPP access gateway, or an UP functional entity supporting the PPPOE.
  • the subscription data includes indication information about whether to allow the UE to access the non-3GPP network, including:
  • the subscription data includes a network access mode parameter, where the network access mode parameter is set to a packet switched domain, or if the network access mode parameter is set to a packet switched domain or a voice service domain, indicating that the UE is allowed to connect Into the non-3GPP network; if the network access mode parameter is set to the voice service domain, it means that the UE is not allowed to access the non-3GPP network.
  • the subscription data includes indication information about whether the UE is allowed to access the non-3GPP network, including:
  • the subscription data includes a non-3GPP permission indication, it indicates that the UE is allowed to access the non-3GPP network; if the subscription data does not include the non-3GPP permission indication, it indicates that the UE is allowed to access the non-3GPP network.
  • the subscription data includes indication information about whether the UE is allowed to access the non-3GPP network, including:
  • the UE is not allowed to access the non-3GPP network; if the subscription data does not include the non-3GPP disallow indication, the UE is allowed to access the non-3GPP.
  • the internet If the subscription data includes a non-3GPP disallow indication, the UE is not allowed to access the non-3GPP network; if the subscription data does not include the non-3GPP disallow indication, the UE is allowed to access the non-3GPP.
  • the CP functional entity 800 further includes a receiving module 803.
  • the obtaining module 801 acquires subscription data of the UE, including:
  • the obtaining module 801 acquires non-3GPP access capability of at least one UP function entity by using a DNS query.
  • the obtaining module 801 acquires the non-3GPP access capability of the configured at least one UP functional entity, where the receiving module 803 is configured to establish, in the at least one UP functional entity, the UP functional entity and the CP functional entity.
  • the connection establishment request message sent by each UP function entity is received, and the connection establishment request message carries the non-3GPP access capability of each UP function entity.
  • the selection module 802 is configured according to the non-3GPP access capability of the at least one UP function entity.
  • the obtaining module 801 is further configured to acquire the non-3GPP access capability of the UE before the target UP function entity that supports the non-3GPP access is selected by the at least one UP function entity.
  • the selecting module 802 selects a target UP function entity that supports non-3GPP access from the at least one UP function entity according to the non-3GPP access capability of the at least one UP function entity, including:
  • the selecting module 802 is configured to: if the UE's non-3GPP access capability indicates that the UE is a UE that supports non-3GPP access, according to the non-3GPP access capability of the at least one UP functional entity, from the at least one UP function. A target UP functional entity supporting non-3GPP access is selected in the entity.
  • the non-3GPP access capability of the UE includes:
  • the UE supports multiple access, the UE supports Wifi access, the UE supports IPSec, the UE supports fixed network access, the UE supports unlicensed spectrum access capability, or the UE supports PPPOE. At least one of them.
  • the CP functional entity 800 further includes a receiving module 803 and a sending module 804.
  • the receiving module 803 is configured to receive the non-access stratum NAS sent by the UE when the UE accesses from the non-3GPP network. Signaling, the NAS signaling carries a PDU session establishment request message.
  • the sending module 804 is configured to send the PDU session establishment request message to the target UP function entity.
  • the receiving module 803 is further configured to receive a PDU session establishment response message sent by the target UP function entity, where the PDU session establishment response message carries an F-TEID of the target UP function entity allocated by the target UP function entity, and the target UP function
  • the entity's F-TEID includes the network protocol IP address of the target UP functional entity and the TEID of the target UP functional entity.
  • the sending module 804 is further configured to send the F-TEID of the target UP function entity to the non-3GPP access gateway N3G-GW.
  • the receiving module 803 is further configured to receive an F-TEID of the N3G-GW allocated by the N3G-GW, where the F-TEID of the N3G-GW includes an IP address of the N3G-GW and a TEID of the N3G-GW.
  • the sending module 804 is further configured to send the F-TEID of the N3G-GW to the target UP function entity.
  • the IP address of the target UP functional entity and the IP address of the N3G-GW are IP addresses of the device granularity, and the TEID of the target UP functional entity and the TEID of the N3G-GW are TEIDs of the device granularity; or
  • the IP address of the target UP functional entity and the IP address of the N3G-GW are the IP addresses of the session granularity, and the TEID of the target UP functional entity and the TEID of the N3G-GW are the TEID of the session granularity.
  • the CP functional entity 800 further includes a sending module 804.
  • the selection module 802 selects a target UP function entity that supports non-3GPP access
  • the selection module 802 is further configured to: before the UE accesses from the non-3GPP network, based on the location of the UE, or whether the N3G-GW is At least one condition that is unified with the target UP functional entity or the load condition of the N3G-GW is that the UE selects the target N3G-GW.
  • the sending module 804 is configured to send the identifier of the target N3G-GW to the UE.
  • the CP functional entity 800 further includes a sending module 804.
  • the sending module 804 is configured to send the identifier of the target UP function entity to the UE before the UE accesses the non-3GPP network,
  • the identifier of the target UP functional entity is used by the UE to select a target N3G-GW that is unified with the target UP functional entity or is closest to the physical location of the target UP functional entity.
  • the CP functional entity 800 further includes a sending module 804.
  • the selection module 802 selects a target UP functional entity that supports non-3GPP access
  • the selection module 802 Also used for when the UE accesses from the non-3GPP network, based on the location of the UE, or whether the N3G-GW is integrated with the target UP functional entity, or the N3G-GW load condition, etc., at least one condition is the UE Select the target N3G-GW.
  • the sending module 804 is configured to send an identifier of the target N3G-GW to the UE by using an initial N3G-GW accessed by the UE.
  • FIG. 9 shows a possible structural diagram of the CP functional entity involved in the foregoing embodiment.
  • the CP functional entity 900 includes: a processing module 901 and a communication module 902. .
  • the processing module 901 can be used to perform the operations that can be performed by the obtaining module 801 and the selecting module 802 in FIG. 8.
  • the communications module 902 can be used to perform operations performed by the receiving module 803 and the sending module 804 in FIG. Referring to the embodiment shown in FIG. 8, the embodiments of the present invention are not described herein again.
  • the CP functional entity is presented in the form of dividing each functional module corresponding to each function, or the CP functional entity is presented in the form of dividing each functional module in an integrated manner.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the CP functional entity 800 or the CP functional entity 900 can take the form shown in FIG.
  • the obtaining module 801, the selecting module 802, the receiving module 803, and the sending module 804 in FIG. 8 can be implemented by the processor 201 and the memory 203 of FIG.
  • the obtaining module 801, the selecting module 802, the receiving module 803, and The sending module 804 can be executed by the processor 201 to call the application code stored in the memory 203, which is not limited by the embodiment of the present invention.
  • the processing module 901 and the communication module 902 in FIG. 9 may be implemented by the processor 201 and the memory 203 of FIG. 2.
  • the processing module 901 and the communication module 902 may be invoked in the memory 203 by the processor 201.
  • the stored application code is executed, and the embodiment of the present invention does not impose any limitation.
  • the embodiment of the invention further provides a computer storage medium for storing computer software instructions used by the CP functional entity, which comprises a program designed to execute the above method embodiment.
  • the UP functional entity selection supporting non-3GPP access can be implemented by executing the stored program.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了支持non-3GPP接入的用户面功能实体选择方法、设备及系统，以至少解决目前当UE从3GPP网络移动到non-3GPP网络接入时，之前选择的UP功能实体将可能不再适合继续为UE服务，从而无法保证业务的连续性的问题。方法包括：当UE从3GPP网络接入的情况下，CP功能实体获取该UE的签约数据，该签约数据中包含是否允许该UE接入non-3GPP网络的指示信息；若该指示信息指示允许该UE接入non-3GPP网络，该CP功能实体选择支持non-3GPP接入的目标UP功能实体。本发明适用于通信技术领域。

Description

支持non-3GPP接入的用户面功能实体选择方法、设备及系统
本申请要求于2016年10月25日提交中国专利局、申请号为201610939201.7、发明名称为“支持non-3GPP接入的用户面功能实体选择方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及支持非-第三代合作伙伴计划(non-3rd generation partnership project，non-3GPP)接入的用户面(user plane，UP)功能实体选择方法、设备及系统。
背景技术
为了应对无线宽带技术的挑战，保持3GPP网络的领先优势，3GPP标准组在2016年底制定了下一代移动通信系统(next generation system)网络架构，称为第五代(5rd generation，5G)网络架构。该架构不但支持3GPP标准组定义的无线技术接入5G核心网络(5G core network)，而且支持non-3GPP接入技术接入5G核心网络。其中5G核心网络的核心网功能分为UP功能与控制面(control plane，CP)功能。UP功能实体主要负责分组数据包的转发、服务质量(quality of service，QoS)控制、计费信息统计等；CP功能实体主要负责向UP下发数据包转发策略、QoS控制策略等。
现有技术中，当用户设备(user equipment，UE)从3GPP网络接入时，CP功能实体为UE选择合适的UP功能实体，进而该UP功能实体与无线侧建立用户面连接，并为UE提供相关的服务。其中，上述合适的UP功能实体指当前负载较低，且可以支持相关的(access point name，APN)的UP功能实体。
然而，当UE从该3GPP网络移动到non-3GPP网络接入时，之前选择的UP功能实体将可能不再适合继续为UE服务，从而无法保证业务的连续性。
发明内容
本发明实施例提供支持non-3GPP接入的用户面功能实体选择方法、设备及系统，以至少解决目前当UE从3GPP网络移动到non-3GPP网络接入时，之前选择的UP功能实体将可能不再适合继续为UE服务，从而无法保证业务的连续性的问题。
为达到上述目的，本发明实施例提供如下技术方案：
第一方面，提供一种支持non-3GPP接入的UP功能实体选择方法，该方法包括：当UE从3GPP网络接入的情况下，CP功能实体获取该UE的签约数据，该签约数据中包含是否允许该UE接入non-3GPP网络的指示信息；若该指示信息指示允许该UE接入non-3GPP网络，该CP功能实体选择支持non-3GPP接入的目标UP功能实体。也就是说，CP功能实体在选择支持 non-3GPP接入的目标UP功能实体时，考虑了是否允许UE接入non-3GPP网络的因素，在允许UE接入non-3GPP网络的情况下，CP功能实体选择支持non-3GPP接入的目标UP功能实体。由于支持non-3GPP接入的目标UP功能实体与non-3GPP接入网关之间存在如图1所示的接口NG3，因此，当UE从该3GPP网络移动到non-3GPP网络接入时，该目标UP功能实体仍适合继续为UE服务，从而可以保证业务的连续性。
在一种可能的设计中，该CP功能实体选择支持non-3GPP接入的目标UP功能实体，包括：该CP功能实体获取至少一个UP功能实体的non-3GPP接入能力；该CP功能实体根据该至少一个UP功能实体的non-3GPP接入能力，从该至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。也就是说，CP功能实体可以基于签约数据和UP功能实体的non-3GPP接入能力选择支持non-3GPP接入的目标UP功能实体。
在一种可能的设计中，该签约数据中包含是否允许该UE接入non-3GPP网络的指示信息，包括：该签约数据中包含网络接入模式参数，其中，若该网络接入模式参数设置为分组交换域、或若该网络接入模式参数设置为分组交换域或语音服务域，则表示允许该UE接入non-3GPP网络；若该网络接入模式参数设置为语音服务域，则表示不允许该UE接入non-3GPP网络；或者，若该签约数据中包含non-3GPP允许指示，则表示允许该UE接入non-3GPP网络；若该签约数据中不包含non-3GPP允许指示，则表示不允许该UE接入non-3GPP网络；或者，若该签约数据中包含non-3GPP不允许指示，则表示不允许该UE接入non-3GPP网络，若该签约数据中不包含non-3GPP不允许指示，则表示允许该UE接入non-3GPP网络。
在一种可能的设计中，该至少一个UP功能实体的non-3GPP接入能力包括：UP功能实体支持网络协议安全连接IPSec、UP功能实体支持与non-3GPP接入网关之间的接口、UP功能实体与non-3GPP接入网关融合、或UP功能实体支持以太网上的点对点协议PPPOE中的至少一种。
在一种可能的设计中，该CP功能实体获取至少一个UP功能实体的non-3GPP接入能力，包括：该CP功能实体通过域名系统DNS查询获取至少一个UP功能实体的non-3GPP接入能力；或者；该CP功能实体获取配置的至少一个UP功能实体的non-3GPP接入能力，其中，该至少一个UP功能实体中的每个UP功能实体与该CP功能实体建立连接时，该CP功能实体接收该每个UP功能实体发送的连接建立请求消息，该连接建立请求消息中携带该每个UP功能实体的non-3GPP接入能力。也就是说，CP功能实体可以通过上述方式获取至少一个UP功能实体的non-3GPP接入能力。
在一种可能的设计中，在该CP功能实体根据该至少一个UP功能实体的non-3GPP接入能力，从该至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体之前，还包括：该CP功能实体获取该UE的non-3GPP接入能力；该CP功能实体根据该至少一个UP功能实体的non-3GPP接入能力，从该至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体，包括：若该UE的non-3GPP接入能力表征该UE为支持non-3GPP接入的UE，该CP功能实体根据该至少一个UP功能实体的non-3GPP接入能力，从该至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。也就是说，CP功能实体在选择支持non-3GPP接入的目标UP功能实体时，不仅考虑了是否允许UE接入non-3GPP网络的因素，还考虑了UE的non-3GPP接入能力。在允许UE接入non-3GPP网络的情况下，若该UE的non-3GPP接入能力表征该UE为支持non-3GPP接入的UE，CP功能实体基于UP功能实体的non-3GPP接入能力选 择支持non-3GPP接入的目标UP功能实体。
在一种可能的设计中，该UE的non-3GPP接入能力包括：该UE支持多接入、该UE支持无线保真Wifi接入、该UE支持IPSec的能力、该UE支持固网接入的能力、该UE支持非授权频谱的接入能力、或该UE支持PPPOE的能力中的至少一种。
在一种可能的设计中，在该CP功能实体选择支持non-3GPP接入的目标UP功能实体之后，还包括：当该UE从non-3GPP网络接入的情况下，该CP功能实体接收该UE发送的非接入层NAS信令，该NAS信令中携带分组数据单元PDU会话建立请求消息；该CP功能实体向该目标UP功能实体发送该PDU会话建立请求消息；该CP功能实体接收该目标UP功能实体发送的PDU会话建立应答消息，该PDU会话建立应答消息携带该目标UP功能实体分配的该目标UP功能实体的全量隧道端点标识F-TEID，该目标UP功能实体的F-TEID包括该目标UP功能实体的网络协议IP地址和该目标UP功能实体的隧道端点标识TEID；该CP功能实体向non-3GPP接入网关N3G-GW发送该目标UP功能实体的F-TEID；该CP功能实体接收该N3G-GW分配的该N3G-GW的F-TEID，该N3G-GW的F-TEID包括该N3G-GW的IP地址和该N3G-GW的TEID；该CP功能实体向该目标UP功能实体发送该N3G-GW的F-TEID。这样，该目标UP功能实体可以获知N3G-GW的F-TEID，N3G-GW可以获知目标UP功能实体的F-TEID，从而可以建立N3G-GW和目标UP之间的会话连接。
在一种可能的设计中，该目标UP功能实体的IP地址和该N3G-GW的IP地址为设备粒度的IP地址，以及该目标UP功能实体的TEID和该N3G-GW的TEID为设备粒度的TEID；或者，该目标UP功能实体的IP地址和该N3G-GW的IP地址为会话粒度的IP地址，以及该目标UP功能实体的TEID和该N3G-GW的TEID为会话粒度的TEID。也就是说，本发明申请中的F-TEID不仅可以是设备粒度的F-TEID，也可以是会话粒度的F-TEID。
在一种可能的设计中，在该CP功能实体选择支持non-3GPP接入的目标UP功能实体之后，该UE从non-3GPP网络接入之前，还包括：该CP功能实体基于该UE的位置、或N3G-GW是否与该目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为该UE选择目标N3G-GW；该CP功能实体向该UE发送该目标N3G-GW的标识。也就是说，UE从3GPP接入的情况下，还基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW，使得可以获取离UE较近的、负荷较低的N3G-GW。
在一种可能的设计中，在该CP功能实体选择支持non-3GPP接入的目标UP功能实体之后，该UE从non-3GPP网络接入之前，还包括：该CP功能实体向该UE发送该目标UP功能实体的标识，该目标UP功能实体的标识用于该UE选择与该目标UP功能实体合一、或者与该目标UP功能实体的物理位置最近的目标N3G-GW。也就是说，UE从3GPP接入的情况下，还基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW，使得可以获取离UE较近的、负荷较低的N3G-GW。
在一种可能的设计中，在该CP功能实体选择支持non-3GPP接入的目标UP功能实体之后，还包括：当该UE从non-3GPP网络接入的情况下，该CP功能实体基于该UE的位置、或N3G-GW是否与该目标UP功能实体合一、或N3G-GW负载情况等至少一个条件为该UE选择目标N3G-GW；该CP功能实体通过该UE接入的初始N3G-GW向该UE发送该目标N3G-GW的标识。也就是说，UE接入non-3GPP网络后，CP功能实体还可以进行N3G-GW重选，并将重新选择的目标N3G-GW标识通知给UE。UE断开与之前N3G-GW的连接，发起到目标N3G-GW的IPSec建立流程。其中， 重新选择的目标N3G-GW是基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件选择的，使得可以获取离UE较近的、负荷较低的N3G-GW，也就是说，UE可以与离UE较近的、负荷较低的N3G-GW建立IPsec连接。
第二方面，本发明的实施例提供一种CP功能实体，该CP功能实体具有实现上述方法实施例中CP功能实体行为的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第三方面，本发明的实施例提供一种CP功能实体，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该CP功能实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该CP功能实体执行如上述第一方面任意一项的non-3GPP接入的UP功能实体选择方法。
第四方面，本发明实施例提供了一种计算机存储介质，用于储存为上述CP功能实体所用的计算机软件指令，其包含用于执行上述方面为CP功能实体所设计的程序。
另外，第二方面至第四方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的5G网络架构示意图；
图2为本发明实施例提供的计算机设备示意图；
图3为本发明实施例提供的一种non-3GPP接入的UP功能实体选择方法流程示意图；
图4为本发明实施例提供的另一种non-3GPP接入的UP功能实体选择方法流程示意图；
图5为本发明实施例提供的又一种non-3GPP接入的UP功能实体选择方法流程示意图；
图6为本发明实施例提供的又一种non-3GPP接入的UP功能实体选择方法流程示意图；
图7为本发明实施例提供的又一种non-3GPP接入的UP功能实体选择方法流程示意图；
图8为本发明实施例提供的一种CP功能实体的结构示意图；
图9为本发明实施例提供的另一种CP功能实体的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。
另外，在本发明的描述中，除非另有说明，“多个”的含义是两个或两个以上。
如图1所示，为本发明实施例提供的5G网络架构。该架构不但支持3GPP标准组定义的无线技术接入5G核心网络，而且支持non-3GPP接入技术接入5G核心网络。
其中，如图1所示，UE从3GPP网络接入时，通过无线接入网络(radio access network，RAN)接入点接入5G核心网络。其中，RAN接入点通过下一代网络接口(next generation，NG)2与5G核心网络的CP功能实体通信，通过NG3与5G核心网络的UP功能实体通信；UE从non-3GPP网络接入时，通过non-3GPP接入网关(non-3GPP gateway，N3G-GW)接入5G核心网络。N3G-GW包含N3G-GW控制面(N3G-GW-C)和N3G-GW用户面(N3G-GW-U)，N3G-GW-C通过NG2与5G核心网络的CP功能实体通信，N3G-GW-U通过NG3与5G核心网络的UP功能实体通信。
另外，上述的CP功能实体通过NG5与5G核心网络的应用功能(application function，AF)实体通信，通过NG4向UP功能实体下发数据包转发策略、QoS控制策略等；上述的UP功能实体通过NG6与5G核心网络的数据网络(data network，DN)实体通信，负责分组数据包的转发、QoS控制、计费信息统计等。
虽然未示出，上述的5G网络架构中还可以包含用户归属服务器(home subscriber server，HSS)，该HSS用于支持处理或调用会话的网络协议(internet protocol，IP)多媒体子系统(IP multimedia subsystem，IMS)网络实体的主要用户数据库。它包含用户配置文件，执行用户的身份验证和授权，并可提供有关用户物理位置的信息，类似于全球移动通信系统(global system for mobile communication，GSM)归属位置寄存器(home location register)。HSS所提供的功能包括IP多媒体功能、分组交换(packet switched，PS)域必需的归属位置寄存器(home location register，HLR)功能及语音服务(call Service，CS)域必需的HLR功能。HSS可处理的信息包括用户识别、编号和地址信息；用户安全信息，即针对鉴权和授权的网络接入控制信息；用户定位信息，即HSS支持用户登记、存储位置信息；用户清单信息等。本发明实施例中，HSS主要用于UE从3GPP网络接入的情况下，提供UE的签约数据，以用于CP功能实体根据该签约数据确定是否允许UE接入non-3GPP网络。
当然，上述的5G网络架构中还可能包含其他模块或者网络实体，本发明实施例对此不作具体限定。
需要说明的是，本申请所涉及到的UE可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的UE，移动台(Mobile station，MS)，终端(terminal)，终端设备(Terminal Equipment)，软终端等等。为方便描述，本申请中，上面提到的设备统称为用户设备或UE。
需要说明的是，上述的“CP功能实体”和“UP功能实体”仅是一个名字，名字本身对设备不构成限定。例如，该“CP功能实体”还有可能被替换为“CP功能”，该“UP功能实体”还有可能被替换为“UP功能”；或者，该“CP功能实体”还有可能被替换为“CP”，该“UP功能实体”还有可能被替换为“UP”，等等，在此进行统一说明，以下不再赘述。
另外，上述5G网络架构中的任意一种功能节点或网元，例如CP功能实体或者UP功能实体，可能由一个实体设备实现，也可能由多个实体设备共同实现；上述5G网络架构中的多个功能节点或网元，例如CP功能实体和UP功能实体可能分别由不同的实体设备实现，也可能都由同一个实体设备实现，本发明实施例对此不作具体限定。即，可以理解的是，上述5G网络架构中的任意一种功能节点或者网元，例如CP功能实体或者UP功能实体，都可能是实体设备内的一个逻辑功能模块，也可能是由多个实体设备组成的一个逻辑功能模块，本发明实施例对此不作具体限定。
例如，如图2所示，图1中的CP功能实体可以通过图2中的计算机设备(或系统)来实现。
图2所示为本发明实施例提供的计算机设备示意图。计算机设备200包括至少一个处理器201，通信总线202，存储器203以及至少一个通信接口204。
处理器201可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线202可包括一通路，在上述组件之间传送信息。
通信接口204，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器203可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器203用于存储执行本发明方案的应用程序代码，并由处理器201来控制执行。处理器201用于执行存储器203中存储的应用程序代码，从而实现non-3GPP接入的UP功能实体选择。
在具体实现中，作为一种实施例，处理器201可以包括一个或多个CPU，例如图2中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备200可以包括多个处理器，例如图2中的处理器201和处理器208。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备200还可以包括输出设备205和输入设备206。输出设备205和处理器201通信，可以以多种方式来显示信息。例如，输出设备205可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备206和处理器201通信，可以以多种方式接受用户的输入。例如，输入设备206可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备200可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备200可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图2中类似结构的设备。本发明实施例不限定计算机设备200的类型。
如图3所示，为本发明实施例提供的non-3GPP接入的UP功能实体选择方法流程示意图。 是以UE从图1所示的5G网络架构中的3GPP网络接入的情况为例进行说明，涉及到UE、RAN接入点、UP功能实体、CP功能实体和HSS之间的交互，包括如下步骤S301-S310：
S301、UE与RAN接入点建立连接，通过RAN接入点向CP功能实体发送附着请求(attach request)消息，以使得CP功能实体接收该附着请求消息。
该附着请求消息中包含UE标识，如UE临时标识或UE永久标识，比如UE永久标识可以为国际移动用户识别码(international mobile subscriber identification number，IMSI)。
可选的，该附着请求消息中还可以包含UE的non-3GPP接入能力，或连接的类型指示中的至少一种。上述non-3GPP接入能力包括：
UE支持多接入、UE支持无线保真(wireless-fidelity，WiFi)接入、UE支持IP安全连接(IP security connection，IPSec)、UE支持固网接入、UE支持非授权频谱的接入、或UE支持以太网上的点对点协议(point-to-point protocol over ethernet，PPPOE)中的至少一种。
上述连接类型指示包括：
UE后续将发起non-3GPP接入指示，或此连接为多连接指示中的至少一种。
S302、CP功能实体向HSS发送签约数据请求，以使得HSS接收该签约数据请求。
其中，该签约数据请求具体可以是签约数据获取消息，或更新位置请求(update location request)消息，本发明实施例对此不作具体限定。上述消息中包含UE永久标识。该UE永久标识可能是通过步骤S301中的附着请求消息携带过来的，也可能是根据步骤S301中的附着请求消息携带过来的UE临时标识获取的，本发明实施例对此不作具体限定。可选的，上述消息中也可能携带该CP功能实体的标识，本发明实施例对此不作具体限定。
S303、HSS根据UE永久标识获取UE的签约数据，该签约数据中包含是否允许UE接入non-3GPP网络的指示信息。
其中，本发明实施例不对通过何种方式在签约数据中指示是否允许UE接入non-3GPP网络做具体限定，示例性的提供如下三种方案：
方案一、签约数据中包含网络接入模式(network access mode)参数，其中，若该网络接入模式参数设置为PS域(PS domain)、或若该网络接入模式参数设置为PS domain或CS domain，则表示允许UE接入non-3GPP网络；若该网络接入模式参数设置为CS domain，则表示不允许UE接入non-3GPP网络。
方案二、若签约数据中包含non-3GPP允许(non-3GPP allowed)指示，则表示允许UE接入non-3GPP网络；若签约数据中不包含non-3GPP允许指示，则表示不允许UE接入non-3GPP网络。
方案三、若签约数据中包含non-3GPP不允许(non-3GPP not allowed)指示，则表示不允许UE接入non-3GPP网络；若签约数据中不包含non-3GPP不允许指示，则表示允许UE接入non-3GPP网络。
可选的，上述的non-3GPP允许指示也可以替换成non-3GPP授权(non-3GPP authorized)指示，本发明实施例对此不作具体限定。
S304、HSS向CP功能实体发送签约数据响应，以使得CP功能实体接收该签约数据响应。
其中，若步骤S302中的签约数据请求具体是签约数据获取消息，则此处的签约数据响应 具体可以是签约数据响应消息；若步骤S302中的签约数据请求具体是更新位置请求(update location request)消息，则此处的签约数据应答具体可以是更新位置响应(update location response)消息，本发明实施例对此不作具体限定。其中，上述消息中包含签约数据。
S305、CP功能实体基于签约数据选择支持non-3GPP接入的目标UP功能实体。
其中，若签约数据中包含的是否允许UE接入non-3GPP网络的指示信息指示允许UE接入non-3GPP网络；或者，若签约数据中包含的是否允许UE接入non-3GPP网络的指示信息指示允许UE接入non-3GPP网络，且，满足如下至少一个条件，即对于支持non-3GPP接入的UE，或对于后续将发起non-3GPP接入的UE或多接入的分组数据单元(packet data unit，PDU)连接，CP功能实体从至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。
可选的，CP功能实体选择支持non-3GPP接入的目标UP功能实体时还考虑UP功能实体的non-3GPP接入能力或UP功能实体支持的用户面类型中的至少一种。
其中，上述的UP功能实体的non-3GPP接入能力包括：
UP功能实体支持IPSec、UP功能实体支持与non-3GPP接入网关之间的接口、UP功能实体与non-3GPP接入网关融合、或UP功能实体支持PPPOE中的至少一种。
上述的UP功能实体支持的用户面类型，包括：
支持建立设备粒度的用户面、或支持建立多接入的用户面中的至少一种。
其中，本发明实施例不对CP功能实体获取UP功能实体的non-3GPP接入能力或UP功能实体支持的用户面类型中的至少一种的方式做具体限定，示例性的提供如下两种方案：
方案一、UP功能实体与CP功能实体建立连接时上报UP功能实体的non-3GPP接入能力或UP功能实体支持的用户面类型中的至少一种。比如，UP功能实体发送Sx接口建立请求(Sx Setup request)消息给CP功能实体，上述消息中含有UP功能实体的non-3GPP接入能力或UP功能实体支持的用户面类型中的至少一种。
方案二、CP功能实体通过域名系统(domain name system，DNS)查询获取UP功能实体的non-3GPP接入能力。比如，在DNS查询过程中，DNS系统将UP功能实体支持的接口信息发送给CP功能实体，上述接口信息中含有与non-3GPP接入网关之间的接口，如图1中的NG3。可选的，DNS向CP功能实体发送UP功能实体支持的用户面类型。
此外，可选的，CP功能实体选择支持non-3GPP接入的目标UP功能实体时还可以考虑UP功能实体当前的负载情况、UP功能实体是否支持相关的APN、UP功能实体的位置信息中的至少一种，本发明实施例对此不作具体限定。
S306、CP功能实体向目标UP功能实体发送PDU会话建立请求(PDU session establishment request)消息，以使得目标UP功能实体接收该PDU会话建立请求消息。
S307、目标UP功能实体为3GPP侧的PDU连接分配目标UP功能实体的全量隧道端点标识(fully qualified tunnel endpoint identifier，F-TEID)，记作F-TEID1，该F-TEID1包括目标UP功能实体的IP地址和目标UP功能实体的隧道端点标识(tunnel endpoint identifier，TEID)。
其中，上述的F-TEID1用于设备内部查找用户上下文，即用户上下文信息所在的具体设备(IP地址对应的设备)的具体处理单板(TEID对应的单板)标识。该F-TEID1可以为设备粒度的F-TEID，即，目标UP功能实体的IP地址为设备粒度的IP地址，目标UP功能实体的TEID为设备粒度的TEID；该F-TEID1也可以为会话粒度的F-TEID，即，目标UP功能实体的 IP地址为会话粒度的IP地址，目标UP功能实体的TEID为会话粒度的TEID，本发明实施例对此不作具体限定。
需要说明的是，这里将目标UP功能实体为3GPP侧的PDU连接分配的目标UP功能实体的F-TEID记作F-TEID1，是为了与下述目标UP功能实体为non-3GPP侧的PDU连接分配的目标UP功能实体的F-TEID进行区分，在此进行统一说明，该说明适用于下述各实施例，以下不再赘述。
S308、目标UP功能实体向CP功能实体发送PDU会话建立响应(PDU session establishment response)消息，该PDU会话建立响应携带F-TEID1，以使得CP功能实体接收该PDU会话建立响应消息。
S309、CP功能实体存储F-TEID1和UE的对应关系，以用于UE在后续的3GPP会话或者3GPP其他流程中根据该对应关系获取该F-TEID1。
S310、CP功能实体通过RAN接入点向UE发送附着响应(attach response)消息，以使得UE接收该附着响应消息。
至此，UE从图1所示的5G网络架构中的3GPP网络接入并且建立PDU会话的过程结束。
上述过程中，CP功能实体在选择支持non-3GPP接入的目标UP功能实体时，考虑了是否允许UE接入non-3GPP网络的因素，在允许UE接入non-3GPP网络的情况下，CP功能实体选择支持non-3GPP接入的目标UP功能实体。由于支持non-3GPP接入的目标UP功能实体与non-3GPP接入网关之间存在如图1所示的接口NG3，因此，当UE从该3GPP网络移动到non-3GPP网络接入时，该目标UP功能实体仍适合继续为UE服务，从而可以保证业务的连续性。
其中，上述S302、S305、S306、S309和S310中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
可选的，在上述步骤S310之后，UE还可以从图1所示的5G网络架构中发起non-3GPP接入和PDU会话建立过程，涉及到UE、N3G接入点、N3G-GW、UP功能实体和CP功能实体之间的交互，该过程中的UP功能实体为上述3GPP接入的情况下选择的目标UP功能实体，该过程包括如下步骤S311-S321：
S311、UE与N3G接入点建立连接，获取N3G-GW标识或N3G-GW的IP地址后，与N3G-GW建立IPSec。
其中，N3G接入点例如可以是WiFi接入点(Access Point，AP)或WiFi接入控制器(Access Control，AC)。
其中，例如可以通过DNS查询方式获取N3G-GW标识或N3G-GW的IP地址。
其中，UE与N3G-GW建立IPSec例如可以是UE通过N3G接入点向N3G-GW发送IKEv2消息，该IKEv2消息具体可以是秘钥交互鉴权(internet key exchange_authenticationIKE_AUTH)消息。该IKE_AUTH消息中可以携带非接入层(non-access stratum，NAS)信令或者扩展的鉴权协议(extensible authentication protocol)EAP信令，本发明实施例对此不做具体限定。本发明实施例以下步骤以该IKE_AUTH消息中可以携带NAS信令为例进行说明。
S312、N3G-GW获取步骤S311中的NAS信令，并通过如图1所示的与CP功能实体之间的接口NG2消息向CP功能实体发送NAS信令，以使得CP功能实体接收该NAS信令。
其中，上述NAS信令例如可以包含PDU会话建立请求(PDU session establishment request)消息。
S313、CP功能实体解析NAS信令，获得PDU会话建立请求消息，并向目标UP功能实体发送PDU会话建立请求消息，以使得目标UP功能实体接收该PDU会话建立请求消息。
其中，该目标UP功能实体为上述实施例中UE从3GPP网络接入的情况下选择的UP功能实体。该UP功能实体的标识和与该UP功能实体对应的APN的对应关系之前可能预先存储在CP功能实体中。当有多个UP功能实体为UE服务时，假设不同的APN对应不同的UP功能实体，则此时需要基于UE当前的APN选择相应的UP功能实体。
S314、目标UP功能实体为non-3GPP侧的PDU连接分配目标UP功能实体的F-TEID，记作F-TEID2。该F-TEID2包括目标UP功能实体的IP地址和目标UP功能实体的TEID。
其中，上述的F-TEID2用于设备内部查找用户上下文，即用户上下文信息所在的具体设备(IP地址对应的设备)的具体处理单板(TEID对应的单板)标识。该F-TEID2可以为设备粒度的F-TEID，即，目标UP功能实体的IP地址为设备粒度的IP地址，目标UP功能实体的TEID为设备粒度的TEID；该F-TEID2也可以为会话粒度的F-TEID，即，目标UP功能实体的IP地址为会话粒度的IP地址，目标UP功能实体的TEID为会话粒度的TEID，本发明实施例对此不作具体限定。
需要说明的是，这里将目标UP功能实体为non-3GPP侧的PDU连接分配的目标UP功能实体的F-TEID记作F-TEID2，是为了与上述目标UP功能实体为3GPP侧的PDU连接分配的目标UP功能实体的F-TEID进行区分，在此进行统一说明，该说明适用于下述各实施例，以下不再赘述。
其中，本发明实施例中的F-TEID1和F-TEID2可能相同，也可能不相同，本发明实施例对此不作具体限定。
S315、目标UP功能实体向CP功能实体发送PDU会话建立响应(PDU session establishment response)消息，该PDU会话建立响应携带F-TEID2，以使得CP功能实体接收该PDU会话建立响应消息。
S316、CP功能实体将F-TEID2通过如图1所示的NG2接口消息发送给N3G-GW。
上述NG2接口消息如连接建立请求消息，或NG2消息等。此外，CP功能实体还可以将发送给UE的NAS信令通过如图1所示的与N3G-GW之间的接口NG2消息发送给N3G-GW。该NAS信令例如可以包含PDU会话建立响应(PDU session establishment response)消息。
S317、N3G-GW存储F-TEID2和UE的对应关系，以用于UE在后续的non-3GPP会话或者non-3GPP其他流程中根据该对应关系获取该F-TEID2。同时，N3G-GW分配N3G-GW的F-TEID，该N3G-GW的F-TEID包含该N3G-GW的IP地址和该N3G-GW的TEID。
其中，该N3G-GW的F-TEID用于设备内部查找用户上下文，即用户上下文信息所在的具体设备(IP地址对应的设备)的具体处理单板(TEID对应的单板)标识。该N3G-GW的F-TEID可以为设备粒度的F-TEID，即，该N3G-GW的IP地址为设备粒度的IP地址，该N3G-GW的TEID为设备粒度的TEID；该N3G-GW的F-TEID也可以为会话粒度的F-TEID，即，该N3G-GW的IP地址为会话粒度的IP地址，该N3G-GW的TEID为会话粒度的TEID，本发明实施例对此不作具体限定。
S318、N3G-GW通过如图1所示的NG2接口消息向CP功能实体发送N3G-GW的F-TEID，以 使得CP功能实体接收该N3G-GW的F-TEID。
其中，上述NG2接口消息例如可以是连接建立响应消息，或NG2消息等。
S319、CP功能实体向目标UP功能实体发送PDU会话更新请求(PDU session modification request)消息，该PDU会话更新请求消息携带N3G-GW的F-TEID，以使得目标UP功能实体接收该PDU会话更新请求消息。
其中，目标UP功能实体在获取N3G-GW的F-TEID之后，可以存储N3G-GW的F-TEID和UE的对应关系，以用于UE在后续的non-3GPP会话或者non-3GPP其他流程中根据该对应关系获取该N3G-GW的F-TEID，本发明实施例对此不作具体限定。
其中，经过步骤S315至步骤S319，目标UP功能实体可以获知N3G-GW的F-TEID，N3G-GW可以获知目标UP功能实体的F-TEID2，从而可以建立N3G-GW和目标UP之间的会话连接。
S320、目标UP功能实体向CP功能实体发送PDU会话更新响应(PDU session modification response)消息，以使得CP功能实体接收该PDU会话更新响应消息。
S321、N3G-GW将步骤S316接收到的CP功能实体发送的NAS信令通过IKEv2消息发送给UE，以使得UE接收该IKEv2消息。
即，N3G-GW将NAS信令封装在IKEv2消息中发送给UE。
需要说明的是，本发明实施例对步骤S317与步骤S321之间的先后关系不作具体限定，具体可以先执行步骤S317，再执行步骤S321；也可以先执行步骤S321，再执行步骤S317；还可以同时执行步骤S317和步骤S321，本发明实施例对此不作具体限定。
至此，UE从图1所示的5G网络架构中的non-3GPP网络接入并且建立PDU会话的过程结束。
上述过程中的UP功能实体为上述3GPP接入的情况下选择的目标UP功能实体，由于在上述3GPP接入的情况下，CP功能实体在选择支持non-3GPP接入的目标UP功能实体时，考虑了是否允许UE接入non-3GPP网络的因素，在允许UE接入non-3GPP网络的情况下，CP功能实体选择支持non-3GPP接入的目标UP功能实体。考虑到支持non-3GPP接入的目标UP功能实体与non-3GPP接入网关之间存在如图1所示的接口NG3，因此，当UE从该3GPP网络移动到该non-3GPP网络接入时，该目标UP功能实体仍适合继续为UE服务，从而可以保证业务的连续性。
其中，上述S313、S316和S319中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
在另一种可能的实现方式中，如图4所示，为本发明实施例提供的另一种non-3GPP接入的UP功能实体选择方法流程示意图。是以UE从图1所示的5G网络架构中的3GPP网络接入的情况为例进行说明，涉及到UE、RAN接入点、UP功能实体、CP功能实体和HSS之间的交互，包括如下步骤S401-S412：
S401-S404、同S301-S304。
S405、同S310。
S406、UE通过RAN接入点向CP功能实体发送PDU会话建立请求(PDU session establishment request)消息，以使得CP功能实体接收该PDU会话建立请求消息。
其中，可选的，若步骤S401中的附着请求消息中没有携带UE的non-3GPP接入能力，或 连接的类型指示中的至少一种，则该PDU会话建立请求消息中可以携带UE的non-3GPP接入能力，或连接的类型指示中的至少一种。
S407、同S305。
S408-S411、同S306-S309。
S412、CP功能实体通过RAN接入点向UE发送PDU会话建立响应(PDU session establishment response)消息，以使得CP功能实体接收该PDU会话建立响应消息。
至此，UE从图1所示的5G网络架构中的3GPP网络接入并且建立PDU会话的过程结束。
上述过程中，CP功能实体在选择支持non-3GPP接入的目标UP功能实体时，考虑了是否允许UE接入non-3GPP网络的因素，在允许UE接入non-3GPP网络的情况下，CP功能实体选择支持non-3GPP接入的目标UP功能实体。由于支持non-3GPP接入的目标UP功能实体与non-3GPP接入网关之间存在如图1所示的接口NG3，因此，当UE从该3GPP网络移动到non-3GPP网络接入时，该目标UP功能实体仍适合继续为UE服务，从而可以保证业务的连续性。
其中，上述S402、S405、S407、S408、S411和S412中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
可选的，在上述步骤S412之后，UE还可以从图1所示的5G网络架构中发起non-3GPP接入和PDU会话建立过程，涉及到UE、N3G接入点、N3G-GW、UP功能实体和CP功能实体之间的交互，该过程中的UP功能实体为上述3GPP接入的情况下选择的目标UP功能实体，该过程的步骤S413-S423同图3所示的实施例中的步骤S311-S321，本发明实施例在此不再赘述。
其中，上述S415、S418、S421中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
同图3所示的实施例的差别在于，本发明实施例中，CP功能实体在3GPP接入的情况下的PDU连接建立流程中完成支持non-3GPP接入的目标UP功能实体的选择，而图3所示的实施例中，CP功能实体在3GPP接入的情况下的附着流程中完成支持non-3GPP接入的目标UP功能实体的选择。另外，本发明实施例中除了可以在附着消息中携带UE的non-3GPP接入能力，或连接的类型指示中的至少一种，还可以在UE发起PDU连接建立时携带UE的non-3GPP接入能力，或连接的类型指示中的至少一种。
在又一种可能的实现方式中，如图5所示，为本发明实施例提供的又一种non-3GPP接入的UP功能实体选择方法流程示意图。是以UE从图1所示的5G网络架构中的3GPP网络接入的情况为例进行说明，涉及到UE、RAN接入点、UP功能实体、CP功能实体和HSS之间的交互，包括如下步骤S501-S511：
S501-S509、同S301-S309。
S510、CP功能实体基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW。
S511、CP功能实体通过RAN接入点向UE发送附着响应(attach response)消息，该附着响应消息携带目标N3G-GW标识，以使得UE接收该附着响应消息。
其中，目标N3G-GW标识例如可以是目标N3G-GW的全称域名(fully qualified domain name，FQDN)，或者目标N3G-GW的IP地址，本发明实施例 对此不作具体限定。
至此，UE从图1所示的5G网络架构中的3GPP网络接入并且建立PDU会话的过程结束。
一方面，上述过程中，CP功能实体在选择支持non-3GPP接入的目标UP功能实体时，考虑了是否允许UE接入non-3GPP网络的因素，在允许UE接入non-3GPP网络的情况下，CP功能实体选择支持non-3GPP接入的目标UP功能实体。由于支持non-3GPP接入的目标UP功能实体与non-3GPP接入网关之间存在如图1所示的接口NG3，因此，当UE从该3GPP网络移动到non-3GPP网络接入时，该目标UP功能实体仍适合继续为UE服务，从而可以保证业务的连续性。另一方面，UE从3GPP接入的情况下，还基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW，使得可以获取离UE较近的、负荷较低的N3G-GW。
其中，上述S502、S505、S506、S509、S510和S511中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
可选的，在上述步骤S511之后，UE还可以从图1所示的5G网络架构中发起non-3GPP接入和PDU会话建立过程，涉及到UE、N3G接入点、目标N3G-GW、UP功能实体和CP功能实体之间的交互，该过程中的UP功能实体为上述3GPP接入的情况下选择的目标UP功能实体，该过程中的N3G-GW为上述3GPP接入的情况下选择的目标N3G-GW，该过程包括如下步骤：
S512、UE与N3G接入点建立连接，发起到目标N3G-GW的IPSec连接。
其中，若步骤S511中的附着响应消息携带的是目标N3G-GW标识不是目标N3G-GW的IP地址，则UE可以基于收到的目标N3G-GW标识通过DNS查询获取该目标N3G-GW的IP地址，进而基于该目标N3G-GW的IP地址，发起到目标N3G-GW的IPSec连接。
若步骤S511中的附着响应消息携带的是目标N3G-GW标识是目标N3G-GW的IP地址，则UE可以直接根据该目标N3G-GW的IP地址，发起到目标N3G-GW的IPSec连接。
其中，UE与N3G-GW建立IPSec例如可以是UE通过N3G接入点向N3G-GW发送IKEv2消息，该IKEv2消息具体可以是IKE_AUTH消息。IKE_AUTH消息中可以携带NAS信令或者EAP信令，本发明实施例对此不做具体限定。本发明实施例以下步骤以该IKE_AUTH消息中可以携带NAS信令为例进行说明。
若步骤S510中选择的目标N3G-GW与目标UP功能实体不可以合一，则本发明实施例后续的步骤可参考图3的步骤S312-S321，区别仅在于将图3的N3G-GW替换为本发明实施例中的目标N3G-GW，本发明实施例在此不再赘述。
若步骤S510中选择的目标N3G-GW与目标UP功能实体可以合一，则如图5所示，在步骤S512之后，还可以包括如下步骤S513和步骤S514：
S513、目标N3G-GW获取步骤S512中的NAS信令，并通过如图1所示的与CP功能实体之间的接口NG2消息向CP功能实体发送NAS信令，以使得CP功能实体接收该NAS信令。
其中，上述NAS信令例如可以包含PDU会话建立响应(PDU session establishment response)消息。
S514、CP功能实体通过IKEv2消息向UE发送NAS信令，以使得UE接收该IKEv2消息。
即，CP功能实体将NAS信令封装在IKEv2消息中发送给UE。
至此，UE从图1所示的5G网络架构中的non-3GPP网络接入并且建立PDU会话的过程结 束。
一方面，上述过程中的UP功能实体为上述3GPP接入的情况下选择的目标UP功能实体，由于在上述3GPP接入的情况下，CP功能实体在选择支持non-3GPP接入的目标UP功能实体时，考虑了是否允许UE接入non-3GPP网络的因素，在允许UE接入non-3GPP网络的情况下，CP功能实体选择支持non-3GPP接入的目标UP功能实体。考虑到支持non-3GPP接入的目标UP功能实体与non-3GPP接入网关之间存在如图1所示的接口NG3，因此，当UE从该3GPP网络移动到该non-3GPP网络接入时，该目标UP功能实体仍适合继续为UE服务，从而可以保证业务的连续性。另一方面，UE从non-3GPP接入的情况下，与上述3GPP接入的情况下选择的目标N3G-GW建立IPsec连接，而该目标N3G-GW是基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件选择的，是离UE较近的、负荷较低的N3G-GW，因此UE可以与离UE较近的、负荷较低的N3G-GW建立IPsec连接。
其中，上述S514中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
在又一种可能的实现方式中，如图6所示，为本发明实施例提供的又一种non-3GPP接入的UP功能实体选择方法流程示意图。是以UE从图1所示的5G网络架构中的3GPP网络接入的情况为例进行说明，涉及到UE、RAN接入点、UP功能实体、CP功能实体和HSS之间的交互，包括如下步骤S601-S613：
S601-S611、同S401-S411。
S612、CP功能实体基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW。
S613、CP功能实体通过RAN接入点向UE PDU会话建立响应(PDU session establishment response)消息，该PDU会话建立响应消息携带目标N3G-GW标识，以使得CP功能实体接收该PDU会话建立响应消息。
其中，目标N3G-GW标识例如可以是目标N3G-GW的FQDN，或者目标N3G-GW的IP地址，本发明实施例对此不作具体限定。
至此，UE从图1所示的5G网络架构中的3GPP网络接入并且建立PDU会话的过程结束。
一方面，上述过程中，CP功能实体在选择支持non-3GPP接入的目标UP功能实体时，考虑了是否允许UE接入non-3GPP网络的因素，在允许UE接入non-3GPP网络的情况下，CP功能实体选择支持non-3GPP接入的目标UP功能实体。由于支持non-3GPP接入的目标UP功能实体与non-3GPP接入网关之间存在如图1所示的接口NG3，因此，当UE从该3GPP网络移动到non-3GPP网络接入时，该目标UP功能实体仍适合继续为UE服务，从而可以保证业务的连续性。另一方面，UE从3GPP接入的情况下，还基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW，使得可以获取离UE较近的、负荷较低的N3G-GW。
其中，上述S602、S605、S607、S608、S611、S612和S613中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
可选的，在上述步骤S613之后，UE还可以从图1所示的5G网络架构中发起non-3GPP接入和PDU会话建立过程，涉及到UE、N3G接入点、目标N3G-GW、UP功能实体和CP功能实 体之间的交互，该过程中的UP功能实体为上述3GPP接入的情况下选择的目标UP功能实体，该过程中的N3G-GW为上述3GPP接入的情况下选择的目标N3G-GW。在步骤S612中选择的目标N3G-GW与目标UP功能实体不可以合一的情况下，本发明实施例后续的步骤可参考图3的步骤S312-S321，区别仅在于将图3的N3G-GW替换为本发明实施例中的目标N3G-GW，本发明实施例在此不再赘述；在步骤S612中选择的目标N3G-GW与目标UP功能实体可以合一的情况下，该过程的步骤S614-S616同图5所示的实施例中的步骤S512-S514，本发明实施例在此不再赘述。
其中，上述S616中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
同图5所示的实施例的差别在于，本发明实施例中，CP功能实体在3GPP接入的情况下的PDU连接建立流程中完成支持non-3GPP接入的目标UP功能实体的选择和目标N3G-GW的选择，而图5所示的实施例中，CP功能实体在3GPP接入的情况下的附着流程中完成支持non-3GPP接入的目标UP功能实体的选择和目标N3G-GW的选择。另外，本发明实施例中除了可以在附着消息中携带UE的non-3GPP接入能力，或连接的类型指示中的至少一种，还可以在UE发起PDU连接建立时携带UE的non-3GPP接入能力，或连接的类型指示中的至少一种。
可选的，在具体实现中，在图5或者图6所示的实施例中，也可以不用CP功能实体基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW，而是在CP功能实体通过RAN接入点向UE发送的附着响应(attach response)消息中或者PDU会话建立响应(PDU session establishment response)消息中携带目标UP功能实体标识，由UE根据该目标UP功能实体标识来确定该目标N3G-GW。具体可以包括：UE获取该目标UP功能实体标识后，基于DNS查询N3G-GW标识，获得N3G-GW标识列表。对于N3G-GW标识列表中的每个N3G-GW标识，比较该N3G-GW标识对应的N3G-GW的FQDN与目标UP功能实体标识对应的目标UP的FQDN字符串匹配程度，优选与UP功能实体合一的N3G-GW作为目标N3G-GW。比较方式如两者的FQDN字符串完全相同，则为合一节点。否则选择与UP功能实体匹配度最高的N3G-GW作为目标N3G-GW，此N3G-GW与目标UP功能实体的物理位置最近。基于上述方式选择目标N3G-GW之后，后续UE从图1所示的5G网络架构中发起non-3GPP接入和PDU会话建立过程可参考图5或者图6所示的实施例，在此不再赘述。
可选的，在具体实现中，也可以不用在UE接入3GPP网络的情况下选择目标N3G-GW，而是在UE接入non-3GPP网络的情况下选择目标N3G-GW。比如，如图7所示，假设UE从图1所示的5G网络架构中的3GPP网络接入并且建立PDU会话的过程的步骤S701-S710同图3所示的实施例中的步骤S301-S310，则在步骤S710之后，还可以包括如下步骤：
S711、同S311。
S712、同S312。
S713、CP功能实体基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW。
S714、CP功能实体将目标N3G-GW标识通过如图1所示的NG2接口消息发送给初始N3G-GW，以使得初始N3G-GW接收该目标N3G-GW标识。
其中，该目标N3G-GW标识的相关描述可参考上述实施例，本发明实施例在此不再赘述。
上述NG2接口消息如连接建立请求消息，或NG2消息等。此外，CP功能实体还可以将发 送给UE的NAS信令通过如图1所示的与N3G-GW之间的接口NG2消息发送给N3G-GW。该NAS信令例如可以包含PDU会话建立响应(PDU session establishment response)消息。
S715、初始N3G-GW将步骤S714接收到的CP功能实体发送的NAS信令和目标N3G-GW标识通过IKEv2消息发送给UE，以使得UE接收该NAS信令和目标N3G-GW标识。同时，初始N3G-GW断开与UE的连接
可选的，上述IKEv2消息中还可以携带重定指示。
S716、UE基于收到的目标N3G-GW标识，发起与目标N3G-GW的连接。
可选的，UE也可以基于重定向指示，发起与目标N3G-GW的连接，本发明实施例对此不作具体限定。
其中，UE发起与目标N3G-GW的连接的过程可参考上述图5或者图6所示的实施例，本发明实施例在此不再赘述。
其中，上述S702、S705、S706、S709、S710、S713和S714中CP功能实体的动作可以由图2所示的计算机设备200中的处理器201调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
同图5或者图6所示的实施例的差别在于，本发明实施例中，UE接入non-3GPP网络后，CP功能实体进行N3G-GW重选，并将重新选择的目标N3G-GW标识通知给UE。UE断开与之前初始N3G-GW的连接，发起到目标N3G-GW的IPSec建立流程。其中，重新选择的目标N3G-GW是基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件选择的，使得可以获取离UE较近的、负荷较低的N3G-GW，基于离UE较近的、负荷较低的N3G-GW发起IPSec建立流程。
可选的，在具体实现中，在图7所示的实施例中，也可以不用CP功能实体基于UE的位置、或N3G-GW是否与目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为UE选择目标N3G-GW，而是在CP功能实体向初始N3G-GW发送的NG2消息中携带目标UP功能实体标识，进而由初始N3G-GW在通过N3G接入点向UE发送的IKEv2消息中携带目标UP功能实体标识，使得UE根据该目标UP功能实体标识来确定该目标N3G-GW。其中，UE根据该目标UP功能实体标识来确定该目标N3G-GW的方式可参考上述实施例，本发明实施例在此不再赘述。基于上述方式选择目标N3G-GW之后，UE可基于该目标N3G-GW标识，发起与目标N3G-GW的连接，具体可参考上述图5或者图6所示的实施例，本发明实施例在此不再赘述。
需要说明的是，在上述N3G-GW重选的过程中，UE从图1所示的5G网络架构中的3GPP网络接入并且建立PDU会话的过程也可以参考图4所示的实施例中的步骤S401-S412，本发明实施例对此不作具体限定。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，上述实现CP功能实体的设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对CP功能实体进行功能模块的划分，例如，可以对 应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，在采用对应各个功能划分各个功能模块的情况下，图8示出了上述实施例中所涉及的CP功能实体的一种可能的结构示意图，该CP功能实体800包括：获取模块801和选择模块802。
该获取模块801，用于当UE从3GPP网络接入的情况下，获取该UE的签约数据，该签约数据中包含是否允许该UE接入non-3GPP网络的指示信息。
该选择模块802，用于若该指示信息指示允许该UE接入non-3GPP网络，选择支持non-3GPP接入的目标UP功能实体。
进一步的，该选择模块802选择支持non-3GPP接入的目标UP功能实体，包括：该选择模块802获取至少一个UP功能实体的non-3GPP接入能力；根据该至少一个UP功能实体的non-3GPP接入能力，从该至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。
具体的，该至少一个UP功能实体的non-3GPP接入能力包括：
UP功能实体支持IPSec、UP功能实体支持与non-3GPP接入网关之间的接口、UP功能实体与non-3GPP接入网关融合、或UP功能实体支持PPPOE中的至少一种。
进一步的，一种可能的实现方式中，该签约数据中包含是否允许该UE接入non-3GPP网络的指示信息，包括：
该签约数据中包含网络接入模式参数，其中，若该网络接入模式参数设置为分组交换域、或若该网络接入模式参数设置为分组交换域或语音服务域，则表示允许该UE接入non-3GPP网络；若该网络接入模式参数设置为语音服务域，则表示不允许该UE接入non-3GPP网络。
另一种可能的实现方式中，该签约数据中包含是否允许该UE接入non-3GPP网络的指示信息，包括：
若该签约数据中包含non-3GPP允许指示，则表示允许该UE接入non-3GPP网络；若该签约数据中不包含non-3GPP允许指示，则表示允许该UE接入non-3GPP网络。
又一种可能的实现方式中，该签约数据中包含是否允许该UE接入non-3GPP网络的指示信息，包括：
若该签约数据中包含non-3GPP不允许指示，则表示不允许该UE接入non-3GPP网络；若该签约数据中不包含non-3GPP不允许指示，则表示允许该UE接入non-3GPP网络。
进一步的，如图8所示，该CP功能实体800还包括接收模块803。
该获取模块801获取该UE的签约数据，包括：
该获取模块801通过DNS查询获取至少一个UP功能实体的non-3GPP接入能力。
或者，该获取模块801获取配置的至少一个UP功能实体的non-3GPP接入能力，其中，该接收模块803用于在该至少一个UP功能实体中的每个UP功能实体与该CP功能实体建立连接时，接收该每个UP功能实体发送的连接建立请求消息，该连接建立请求消息中携带该每个UP功能实体的non-3GPP接入能力。
进一步的，在该选择模块802根据该至少一个UP功能实体的non-3GPP接入能力，从该 至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体之前，该获取模块801，还用于获取该UE的non-3GPP接入能力。
该选择模块802根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体，包括：
选择模块802，用于若该UE的non-3GPP接入能力表征该UE为支持non-3GPP接入的UE，根据该至少一个UP功能实体的non-3GPP接入能力，从该至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。
具体的，该UE的non-3GPP接入能力包括：
该UE支持多接入、该UE支持Wifi接入、该UE支持IPSec的能力、该UE支持固网接入的能力、该UE支持非授权频谱的接入能力、或该UE支持PPPOE的能力中的至少一种。
进一步的，如图8所示，该CP功能实体800还包括接收模块803和发送模块804。
在该选择模块802选择支持non-3GPP接入的目标UP功能实体之后，该接收模块803，用于当该UE从non-3GPP网络接入的情况下，接收该UE发送的非接入层NAS信令，该NAS信令中携带PDU会话建立请求消息。
该发送模块804，用于向该目标UP功能实体发送该PDU会话建立请求消息；
该接收模块803，还用于接收该目标UP功能实体发送的PDU会话建立应答消息，该PDU会话建立应答消息携带该目标UP功能实体分配的该目标UP功能实体的F-TEID，该目标UP功能实体的F-TEID包括该目标UP功能实体的网络协议IP地址和该目标UP功能实体的TEID。
该发送模块804，还用于向non-3GPP接入网关N3G-GW发送该目标UP功能实体的F-TEID。
该接收模块803，还用于接收该N3G-GW分配的该N3G-GW的F-TEID，该N3G-GW的F-TEID包括该N3G-GW的IP地址和该N3G-GW的TEID。
该发送模块804，还用于向该目标UP功能实体发送该N3G-GW的F-TEID。
具体的，该目标UP功能实体的IP地址和该N3G-GW的IP地址为设备粒度的IP地址，以及该目标UP功能实体的TEID和该N3G-GW的TEID为设备粒度的TEID；或者，该目标UP功能实体的IP地址和该N3G-GW的IP地址为会话粒度的IP地址，以及该目标UP功能实体的TEID和该N3G-GW的TEID为会话粒度的TEID。
进一步的，一种可能的实现方式中，如图8所示，该CP功能实体800还包括发送模块804。
在该选择模块802选择支持non-3GPP接入的目标UP功能实体之后，该选择模块802，还用于在该UE从non-3GPP网络接入之前，基于该UE的位置、或N3G-GW是否与该目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为该UE选择目标N3G-GW。
该发送模块804，用于向该UE发送该目标N3G-GW的标识。
另一种可能的实现方式中，如图8所示，该CP功能实体800还包括发送模块804。
在该选择模块802选择支持non-3GPP接入的目标UP功能实体之后，该发送模块804，用于在该UE从non-3GPP网络接入之前，向该UE发送该目标UP功能实体的标识，该目标UP功能实体的标识用于该UE选择与该目标UP功能实体合一、或者与该目标UP功能实体的物理位置最近的目标N3G-GW。
又一种可能的实现方式中，如图8所示，该CP功能实体800还包括发送模块804。
在该选择模块802选择支持non-3GPP接入的目标UP功能实体之后，该选择模块802， 还用于当该UE从non-3GPP网络接入的情况下，基于该UE的位置、或N3G-GW是否与该目标UP功能实体合一、或N3G-GW负载情况等至少一个条件为该UE选择目标N3G-GW。
该发送模块804，用于通过该UE接入的初始N3G-GW向该UE发送该目标N3G-GW的标识。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
以采用集成的方式划分各个功能模块的情况下，图9示出了上述实施例中所涉及的CP功能实体的一种可能的结构示意图，该CP功能实体900包括：处理模块901和通信模块902。其中，该处理模块901可用于执行图8中获取模块801和选择模块802所能执行的操作，该通信模块902可用于执行图8中接收模块803和发送模块804所能执行的操作，具体可参考图8所示的实施例，本发明实施例在此不再赘述。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该CP功能实体以对应各个功能划分各个功能模块的形式来呈现，或者，该CP功能实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到CP功能实体800或者CP功能实体900可以采用图2所示的形式。比如，图8中的获取模块801、选择模块802、接收模块803和发送模块804可以通过图2的处理器201和存储器203来实现，具体的，获取模块801、选择模块802、接收模块803和发送模块804可以通过由处理器201来调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。或者，比如，图9中的处理模块901和通信模块902可以通过图2的处理器201和存储器203来实现，具体的，处理模块901和通信模块902可以通过由处理器201来调用存储器203中存储的应用程序代码来执行，本发明实施例对此不作任何限制。
本发明实施例还提供了一种计算机存储介质，用于储存为上述CP功能实体所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。通过执行存储的程序，可以实现支持non-3GPP接入的UP功能实体选择。
尽管在此结合各实施例对本发明进行了描述，然而，在实施所要求保护的本发明过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
本领域技术人员应明白，本发明的实施例可提供为方法、装置(设备)、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。计算机程序存储/分布在合适的介质中，与其它硬件一起提供或作为硬件的一部分，也可以采用其他分布形式，如通过Internet或其它有线或无线电信系统。
本发明是参照本发明实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (25)

  1. 一种支持非-第三代合作伙伴计划non-3GPP接入的用户面UP功能实体选择方法，其特征在于，所述方法包括：
    当用户设备UE从3GPP网络接入的情况下，控制面CP功能实体获取所述UE的签约数据，所述签约数据中包含是否允许所述UE接入non-3GPP网络的指示信息；
    若所述指示信息指示允许所述UE接入non-3GPP网络，所述CP功能实体选择支持non-3GPP接入的目标UP功能实体。
  2. 根据权利要求1所述的方法，其特征在于，所述CP功能实体选择支持non-3GPP接入的目标UP功能实体，包括：
    所述CP功能实体获取至少一个UP功能实体的non-3GPP接入能力；
    所述CP功能实体根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。
  3. 根据权利要求1或2所述的方法，其特征在于，所述签约数据中包含是否允许所述UE接入non-3GPP网络的指示信息，包括：
    所述签约数据中包含网络接入模式参数，其中，若所述网络接入模式参数设置为分组交换域、或若所述网络接入模式参数设置为分组交换域或语音服务域，则表示允许所述UE接入non-3GPP网络；
    或者，若所述签约数据中包含non-3GPP允许指示，则表示允许所述UE接入non-3GPP网络；
    或者，若所述签约数据中包含non-3GPP不允许指示，则表示不允许所述UE接入non-3GPP网络。
  4. 根据权利要求2或3所述的方法，其特征在于，所述至少一个UP功能实体的non-3GPP接入能力包括：
    UP功能实体支持网络协议安全连接IPSec、所述UP功能实体支持与non-3GPP接入网关之间的接口、所述UP功能实体与non-3GPP接入网关融合、或所述UP功能实体支持以太网上的点对点协议PPPOE中的至少一种。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，所述CP功能实体获取至少一个UP功能实体的non-3GPP接入能力，包括：
    所述CP功能实体通过域名系统DNS查询获取至少一个UP功能实体的non-3GPP接入能力；或者；
    所述CP功能实体获取配置的至少一个UP功能实体的non-3GPP接入能力，其中，所述至少一个UP功能实体中的每个UP功能实体与所述CP功能实体建立连接时，所述CP功能实体接收所述每个UP功能实体发送的连接建立请求消息，所述连接建立请求消息中携带所述每个UP功能实体的non-3GPP接入能力。
  6. 根据权利要求2-5任一项所述的方法，其特征在于，在所述CP功能实体根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体之前，还包括：
    所述CP功能实体获取所述UE的non-3GPP接入能力；
    所述CP功能实体根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体，包括：
    若所述UE的non-3GPP接入能力表征所述UE为支持non-3GPP接入的UE，所述CP功能实体根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。
  7. 根据权利要求6所述的方法，其特征在于，所述UE的non-3GPP接入能力包括：
    所述UE支持多接入、所述UE支持无线保真Wifi接入、所述UE支持IPSec的能力、所述UE支持固网接入的能力、所述UE支持非授权频谱的接入能力、或所述UE支持PPPOE的能力中的至少一种。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，在所述CP功能实体选择支持non-3GPP接入的目标UP功能实体之后，还包括：
    当所述UE从non-3GPP网络接入的情况下，所述CP功能实体接收所述UE发送的非接入层NAS信令，所述NAS信令中携带分组数据单元PDU会话建立请求消息；
    所述CP功能实体向所述目标UP功能实体发送所述PDU会话建立请求消息；
    所述CP功能实体接收所述目标UP功能实体发送的PDU会话建立应答消息，所述PDU会话建立应答消息携带所述目标UP功能实体分配的所述目标UP功能实体的全量隧道端点标识F-TEID，所述目标UP功能实体的F-TEID包括所述目标UP功能实体的网络协议IP地址和所述目标UP功能实体的隧道端点标识TEID；
    所述CP功能实体向non-3GPP接入网关N3G-GW发送所述目标UP功能实体的F-TEID；
    所述CP功能实体接收所述N3G-GW分配的所述N3G-GW的F-TEID，所述N3G-GW的F-TEID包括所述N3G-GW的IP地址和所述N3G-GW的TEID；
    所述CP功能实体向所述目标UP功能实体发送所述N3G-GW的F-TEID。
  9. 根据权利要求8所述的方法，其特征在于，所述目标UP功能实体的IP地址和所述N3G-GW的IP地址为设备粒度的IP地址，以及所述目标UP功能实体的TEID和所述N3G-GW的TEID为设备粒度的TEID；
    或者，所述目标UP功能实体的IP地址和所述N3G-GW的IP地址为会话粒度的IP地址，以及所述目标UP功能实体的TEID和所述N3G-GW的TEID为会话粒度的TEID。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，在所述CP功能实体选择支持non-3GPP接入的目标UP功能实体之后，所述UE从non-3GPP网络接入之前，还包括：
    所述CP功能实体基于所述UE的位置、或N3G-GW是否与所述目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为所述UE选择目标N3G-GW；
    所述CP功能实体向所述UE发送所述目标N3G-GW的标识。
  11. 根据权利要求1-9任一项所述的方法，其特征在于，在所述CP功能实体选择支持non-3GPP接入的目标UP功能实体之后，所述UE从non-3GPP网络接入之前，还包括：
    所述CP功能实体向所述UE发送所述目标UP功能实体的标识，所述目标UP功能实体的标识用于所述UE选择与所述目标UP功能实体合一、或者与所述目标UP功能实体的物理位置最近的目标N3G-GW。
  12. 根据权利要求1-9任一项所述的方法，其特征在于，在所述CP功能实体选择支持non-3GPP接入的目标UP功能实体之后，还包括：
    当所述UE从non-3GPP网络接入的情况下，所述CP功能实体基于所述UE的位置、或N3G-GW 是否与所述目标UP功能实体合一、或N3G-GW负载情况等至少一个条件为所述UE选择目标N3G-GW；
    所述CP功能实体通过所述UE接入的初始N3G-GW向所述UE发送所述目标N3G-GW的标识。
  13. 一种控制面CP功能实体，其特征在于，所述CP功能实体包括：获取模块和选择模块；
    所述获取模块，用于当用户设备UE从第三代合作伙伴计划3GPP网络接入的情况下，获取所述UE的签约数据，所述签约数据中包含是否允许所述UE接入non-3GPP网络的指示信息；
    所述选择模块，用于若所述指示信息指示允许所述UE接入non-3GPP网络，选择支持非-第三代合作伙伴计划non-3GPP接入的目标用户面UP功能实体。
  14. 根据权利要求13所述的CP功能实体，其特征在于，所述选择模块选择支持non-3GPP接入的目标UP功能实体，包括：
    所述选择模块获取至少一个UP功能实体的non-3GPP接入能力；
    根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。
  15. 根据权利要求13或14所述的CP功能实体，其特征在于，所述签约数据中包含是否允许所述UE接入non-3GPP网络的指示信息，包括：
    所述签约数据中包含网络接入模式参数，其中，若所述网络接入模式参数设置为分组交换域、或若所述网络接入模式参数设置为分组交换域或语音服务域，则表示允许所述UE接入non-3GPP网络；
    或者，若所述签约数据中包含non-3GPP允许指示，则表示允许所述UE接入non-3GPP网络；
    或者，若所述签约数据中包含non-3GPP不允许指示，则表示不允许所述UE接入non-3GPP网络。
  16. 根据权利要求14或15所述的CP功能实体，其特征在于，所述至少一个UP功能实体的non-3GPP接入能力包括：
    UP功能实体支持网络协议安全连接IPSec、所述UP功能实体支持与non-3GPP接入网关之间的接口、所述UP功能实体与non-3GPP接入网关融合、或所述UP功能实体支持以太网上的点对点协议PPPOE中的至少一种。
  17. 根据权利要求14-16任一项所述的CP功能实体，其特征在于，所述CP功能实体还包括接收模块；
    所述获取模块获取所述UE的签约数据，包括：
    所述获取模块通过域名系统DNS查询获取至少一个UP功能实体的non-3GPP接入能力；或者；
    所述获取模块获取配置的至少一个UP功能实体的non-3GPP接入能力，其中，所述接收模块用于在所述至少一个UP功能实体中的每个UP功能实体与所述CP功能实体建立连接时，接收所述每个UP功能实体发送的连接建立请求消息，所述连接建立请求消息中携带所述每个UP功能实体的non-3GPP接入能力。
  18. 根据权利要求14-17任一项所述的CP功能实体，其特征在于，在所述选择模块根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体之前，所述获取模块，还用于获取所述UE的non-3GPP接 入能力；
    所述选择模块根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体，包括：
    所述选择模块，用于若所述UE的non-3GPP接入能力表征所述UE为支持non-3GPP接入的UE，根据所述至少一个UP功能实体的non-3GPP接入能力，从所述至少一个UP功能实体中选择支持non-3GPP接入的目标UP功能实体。
  19. 根据权利要求18所述的CP功能实体，其特征在于，所述UE的non-3GPP接入能力包括：
    所述UE支持多接入、所述UE支持无线保真Wifi接入、所述UE支持IPSec的能力、所述UE支持固网接入的能力、所述UE支持非授权频谱的接入能力、或所述UE支持PPPOE的能力中的至少一种。
  20. 根据权利要求13-19任一项所述的CP功能实体，其特征在于，所述CP功能实体还包括接收模块和发送模块；
    在所述选择模块选择支持non-3GPP接入的目标UP功能实体之后，所述接收模块，用于当所述UE从non-3GPP网络接入的情况下，接收所述UE发送的非接入层NAS信令，所述NAS信令中携带分组数据单元PDU会话建立请求消息；
    所述发送模块，还用于向所述目标UP功能实体发送所述PDU会话建立请求消息；
    所述接收模块，还用于接收所述目标UP功能实体发送的PDU会话建立应答消息，所述PDU会话建立应答消息携带所述目标UP功能实体分配的所述目标UP功能实体的全量隧道端点标识F-TEID，所述目标UP功能实体的F-TEID包括所述目标UP功能实体的网络协议IP地址和所述目标UP功能实体的隧道端点标识TEID；
    所述发送模块，还用于向non-3GPP接入网关N3G-GW发送所述目标UP功能实体的F-TEID；
    所述接收模块，还用于接收所述N3G-GW分配的所述N3G-GW的F-TEID，所述N3G-GW的F-TEID包括所述N3G-GW的IP地址和所述N3G-GW的TEID；
    所述发送模块，还用于向所述目标UP功能实体发送所述N3G-GW的F-TEID。
  21. 根据权利要求20所述的CP功能实体，其特征在于，所述目标UP功能实体的IP地址和所述N3G-GW的IP地址为设备粒度的IP地址，以及所述目标UP功能实体的TEID和所述N3G-GW的TEID为设备粒度的TEID；
    或者，所述目标UP功能实体的IP地址和所述N3G-GW的IP地址为会话粒度的IP地址，以及所述目标UP功能实体的TEID和所述N3G-GW的TEID为会话粒度的TEID。
  22. 根据权利要求13-21任一项所述的CP功能实体，其特征在于，所述CP功能实体还包括发送模块；
    在所述选择模块选择支持non-3GPP接入的目标UP功能实体之后，所述选择模块，还用于所述UE从non-3GPP网络接入之前，基于所述UE的位置、或N3G-GW是否与所述目标UP功能实体合一、或N3G-GW的负载情况等至少一个条件为所述UE选择目标N3G-GW；
    所述发送模块，用于向所述UE发送所述目标N3G-GW的标识。
  23. 根据权利要求13-21任一项所述的CP功能实体，其特征在于，所述CP功能实体还包括发送模块；
    在所述选择模块选择支持non-3GPP接入的目标UP功能实体之后，所述发送模块，用于所述UE从non-3GPP网络接入之前，向所述UE发送所述目标UP功能实体的标识，所述目标 UP功能实体的标识用于所述UE选择与所述目标UP功能实体合一、或者与所述目标UP功能实体的物理位置最近的目标N3G-GW。
  24. 根据权利要求13-21任一项所述的CP功能实体，其特征在于，所述CP功能实体还包括发送模块；
    在所述选择模块选择支持non-3GPP接入的目标UP功能实体之后，所述选择模块，还用于当所述UE从non-3GPP网络接入的情况下，基于所述UE的位置、或N3G-GW是否与所述目标UP功能实体合一、或N3G-GW负载情况等至少一个条件为所述UE选择目标N3G-GW；
    所述发送模块，用于通过所述UE接入的初始N3G-GW向所述UE发送所述目标N3G-GW的标识。
  25. 一种控制面CP功能实体，其特征在于，包括：处理器、存储器、总线和通信接口；
    所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述CP功能实体运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述CP功能实体执行如权利要求1-12中任意一项所述的支持非-第三代合作伙伴计划non-3GPP接入的用户面UP功能实体选择方法。
PCT/CN2017/105363 2016-10-25 2017-10-09 支持non-3GPP接入的用户面功能实体选择方法、设备及系统 WO2018077023A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17864628.7A EP3503624B1 (en) 2016-10-25 2017-10-09 Method, device and system for selecting user plane functional entity supporting non-3gpp access
US16/382,746 US10952114B2 (en) 2016-10-25 2019-04-12 Method, device, and system for selecting user plane functional entity supporting non-3GPP access

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610939201.7A CN107979860B (zh) 2016-10-25 2016-10-25 支持non-3GPP接入的用户面功能实体选择方法、设备及系统
CN201610939201.7 2016-10-25

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/382,746 Continuation US10952114B2 (en) 2016-10-25 2019-04-12 Method, device, and system for selecting user plane functional entity supporting non-3GPP access

Publications (1)

Publication Number Publication Date
WO2018077023A1 true WO2018077023A1 (zh) 2018-05-03

Family

ID=62004170

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/105363 WO2018077023A1 (zh) 2016-10-25 2017-10-09 支持non-3GPP接入的用户面功能实体选择方法、设备及系统

Country Status (4)

Country Link
US (1) US10952114B2 (zh)
EP (1) EP3503624B1 (zh)
CN (1) CN107979860B (zh)
WO (1) WO2018077023A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113260016A (zh) * 2021-07-05 2021-08-13 深圳艾灵网络有限公司 多模终端接入控制方法、装置、电子设备及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SG11201911748XA (en) * 2017-08-07 2020-01-30 Guangdong Oppo Mobile Telecommunications Corp Ltd Service access method and device
TWI724422B (zh) * 2018-05-17 2021-04-11 新加坡商聯發科技（新加坡）私人有限公司 5g行動通訊中之無線通訊方法
JP7189316B2 (ja) 2018-07-20 2022-12-13 オッポ広東移動通信有限公司 セッション管理方法、端末装置とネットワーク装置
US10750553B2 (en) * 2018-09-25 2020-08-18 Cisco Technology, Inc. Systems and methods for selection of collocated nodes in 5G network
CN115643562A (zh) * 2021-07-19 2023-01-24 华为技术有限公司 一种通信方法及装置
CN115835337A (zh) * 2022-11-29 2023-03-21 广州爱浦路网络技术有限公司 基于5g核心网选择tngf网元的方法、系统和介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127652A (zh) * 2006-08-17 2008-02-20 华为技术有限公司 一种确定用户终端访问外部网络锚点的方法、装置及系统
WO2009117705A1 (en) * 2008-03-21 2009-09-24 Qualcomm Incorporated Address redirection for nodes with multiple internet protocol addresses in a wireless network

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102523570B (zh) * 2006-06-15 2015-11-25 华为技术有限公司 一种网络侧用户面实体选择方法和装置
EP2051549A1 (en) * 2007-10-18 2009-04-22 Nokia Siemens Networks Oy Roaming broker and network interworking control gateway
GB2457656C (en) * 2008-02-18 2014-09-17 Sony Corp Cellular communication system, apparatus and method for network discovery
US8566455B1 (en) * 2008-12-17 2013-10-22 Marvell International Ltd. Method and apparatus for supporting multiple connections in 3GPP systems
US9001682B2 (en) * 2011-07-21 2015-04-07 Movik Networks Content and RAN aware network selection in multiple wireless access and small-cell overlay wireless access networks
WO2013150500A2 (en) * 2012-04-05 2013-10-10 Telefonaktiebolaget L M Ericsson (Publ) Qci based offloading
WO2014107358A1 (en) * 2013-01-03 2014-07-10 Intel Corporation Packet data connections in a wireless communication system using a wireless local area network
CN104427006A (zh) * 2013-08-22 2015-03-18 中兴通讯股份有限公司 网络地址的处理方法、装置、系统、wlan及ue
CN106341907B (zh) * 2015-07-09 2021-03-16 中兴通讯股份有限公司 一种数据传输方法、装置和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127652A (zh) * 2006-08-17 2008-02-20 华为技术有限公司 一种确定用户终端访问外部网络锚点的方法、装置及系统
WO2009117705A1 (en) * 2008-03-21 2009-09-24 Qualcomm Incorporated Address redirection for nodes with multiple internet protocol addresses in a wireless network

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Discussion of Control and User Plane Split", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #109 S 5- 165186, 2 September 2016 (2016-09-02), XP051131280 *
MOTOROLA MOBILITY ET AL.: "Solution: Standalone Non-3GPP Access via NG2/NG3", SA WG 2 MEETING #118 S 2-165650, 21 October 2016 (2016-10-21), XP051155237 *
See also references of EP3503624A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113260016A (zh) * 2021-07-05 2021-08-13 深圳艾灵网络有限公司 多模终端接入控制方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
EP3503624B1 (en) 2023-05-31
EP3503624A4 (en) 2019-07-31
CN107979860A (zh) 2018-05-01
US10952114B2 (en) 2021-03-16
EP3503624A1 (en) 2019-06-26
CN107979860B (zh) 2020-07-07
US20190239133A1 (en) 2019-08-01

Similar Documents

Publication Publication Date Title
WO2018077023A1 (zh) 支持non-3GPP接入的用户面功能实体选择方法、设备及系统
JP7252305B2 (ja) データ伝送方法、デバイス、およびシステム
TWI655877B (zh) 用以選擇網路切片的使用者設備註冊方法、及使用此方法的網路控制器與網路通訊系統
RU2729048C1 (ru) Способ, устройство и система межсистемного хэндовера
JP7422092B2 (ja) 事前に関連付けられた状態で受信されるネットワークアドレスポリシ情報
WO2019128671A1 (zh) 会话建立方法、设备及系统
WO2019011203A1 (zh) 设备接入方法、设备及系统
WO2019157864A1 (zh) 确定位置信息的方法及装置
WO2012095021A1 (zh) 本地ip接入连接建立方法、系统和设备
WO2019042182A1 (zh) 数据传输方法、设备及系统
WO2012100684A1 (zh) 一种控制接入本地网络的方法及装置
WO2019024744A1 (zh) 获取终端设备的身份标识的方法及装置
WO2018090800A1 (zh) 连接建立方法、设备及系统
US20240098583A1 (en) PDU session continuity for a UE moving between a telecommunications network and a gateway device
CN116746213A (zh) 涉及网关设备的系统中的ue的服务数据流连续性
WO2017129101A1 (zh) 路由控制方法、装置及系统
WO2015157981A1 (zh) 一种无线局域网用户侧设备及信息处理方法
WO2017045197A1 (zh) 接入本地网络的方法和相关设备
CN108377493B (zh) 连接建立方法、设备及系统
WO2015196580A1 (zh) 一种无线设备的接入方法、网关设备和无线网络
WO2015135278A1 (zh) 一种鉴权认证方法和系统、ProSe功能实体以及UE
WO2018103732A1 (zh) 一种紧急号码的配置、获取方法及装置
WO2018107490A1 (zh) non-GBR承载上数据传输速率的控制方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17864628

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017864628

Country of ref document: EP

Effective date: 20190320

NENP Non-entry into the national phase

Ref country code: DE