WO2018000654A1 - 本地ip接入业务实现方法及装置、系统、家庭演进基站 - Google Patents

本地ip接入业务实现方法及装置、系统、家庭演进基站 Download PDF

Info

Publication number
WO2018000654A1
WO2018000654A1 PCT/CN2016/101629 CN2016101629W WO2018000654A1 WO 2018000654 A1 WO2018000654 A1 WO 2018000654A1 CN 2016101629 W CN2016101629 W CN 2016101629W WO 2018000654 A1 WO2018000654 A1 WO 2018000654A1
Authority
WO
WIPO (PCT)
Prior art keywords
local
base station
evolved base
home evolved
local gateway
Prior art date
Application number
PCT/CN2016/101629
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 中兴通讯股份有限公司
Publication of WO2018000654A1 publication Critical patent/WO2018000654A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • the present disclosure relates to the field of communications, for example, to a local IP access service implementation method and apparatus, system, and home evolved base station.
  • the Local IP Access (LIPA) service can be used for a single residential or enterprise network, and the LIPA technology proposed by the 3rd Generation Partnership Project (3GPP).
  • the user's local service data can be directly offloaded from the local (home/enterprise) base station.
  • the pressure on the core network after the rapid increase of IP data traffic is avoided, and the routing efficiency of the IP data packet is also improved. This not only reduces the burden on the core network, reduces the core network throughput and transmission cost of the operator, but also reduces the data transmission delay of the user's local data access.
  • the LIPA technology is an enhancement of the function of the Home evolved Node-B (HeNB), which allows the terminal to directly access the IP resources of the local network through the HeNB, and is generally used for the local service service of the operator based on the HeNB.
  • HeNB Home evolved Node-B
  • the 23.401 protocol of 3GPP proposes that the connection enabling LIPA does not support Handover (H0):
  • the Mobile Management Entity receives the Path Switch Request message when the MME determines that the LIPA connection has not been released.
  • the MME will reply with the path switch request failure message (Path Switch Request). Failure message) to the target HeNB;
  • the MME receives a Handover Request message. If the MME determines that the LIPA connection is not released, the MME will reply the Hand Over Failure (Cause) message to the target HeNB.
  • the MME will reply the Hand Over Failure (Cause) message to the target HeNB.
  • LGW Local Gateway
  • the IP address is obtained from the security gateway (SeGW), and then registered with the DNS server.
  • the registration content may include: LHN ID, L-GW. @LN address or L-GW local Fully qualified domain name (Fully Qualified Domain Name, FQDN), SeGW assigned L-GW@CN address.
  • PDN Public Data Network
  • UE User Equipment
  • a DNS request is initiated to the DNS server, and the DNS server returns one or more eligible LGW IP addresses to the MME. ;
  • Each HeNB itself can configure all L-GW@LN addresses or FQDNs connected to the LGW.
  • the HeNB obtains the L-GW@CN address through the Sxx port.
  • the HeNB reports the L-GW@CN address or FQDNs to the MME through the S1 message.
  • the core network MME selects an L-GW in the L-GW List provided by the HeNB.
  • the original H(e)NB requirement document (3GPPTS22.220) has only the concept of LIPA.
  • the application scenario is based on H(e)NB users, and the service can be a home/enterprise network service, or It is an Internet business.
  • the SIPTO concept was proposed.
  • the R12 protocol of 3GPP is a combination of the mobility of LIPA and the SIPTO technology of the local network, collectively referred to as LIMONET.
  • the R12 protocol clearly stipulates that the Serving Gateway (SGW) sinks to the local area and is integrated with the L-GW.
  • SGW Serving Gateway
  • the HeNB initializes the user equipment message (initial UE message), and the uplink non-access
  • the uplink (Non-Acess Stratum) NAS transport, the handover notification and the path switch request message carry the LHN ID to the MME, and the MME has the same LHN ID of the source HeNB and the target HeNB. In this case, switching with SIPTO is supported.
  • the R12 protocol can stipulate that, from the form of service, LIPA is used for services in H(e)NB, and SIPTO is used for public network services; from the network architecture, LIPA is used for H(e)NB, and SIPTO Can be used for H(e)NB or for macro networks.
  • the L-GW external resident deployment scheme using the Selected IP Traffic Offload (SIPTO) of the related art also has certain defects, including:
  • the service service of the terminal depends on the communication guarantee of the three interfaces of S1-C, S5 and AP-LGW. Any abnormality of the link will cause the terminal to drop the call, and the network maintenance is complicated;
  • the LGW When the LGW is deployed as an independent NE, it needs to implement the communication of the S11/S5 port. Because of the LGW resident deployment, the problem of access resources needs to be solved. If the dedicated line access is adopted, the transmission resource depends heavily on the Security considerations require a dedicated computer room. If the shared transmission resource is used for access, in order to ensure security, the various transport protocols and security protocols required by the LGW to support network access, such as IPSec, are inconvenient for network management and deployment.
  • the LGW deployment mode and location limitation of the LIPA system in the related art are limited by the communication requirements between the LGW and the MME, and the flexibility is not high, and the various transport protocols and security protocols required by the LGW to support network access are required. .
  • the present disclosure provides a method, a device, and a home evolved base station for implementing local IP access services, which can solve the problem that the LGW deployment mode and location limitation of the LIPA system are limited by the communication requirements between the LGW and the MME.
  • an embodiment of the present disclosure provides a method for managing a local IP access service, including:
  • the home evolved base station receives an access request of the local IP access service sent by the user terminal;
  • the home evolved base station obtains the network address of the local gateway, and generates bearer information of the local IP access service, where the network address of the local gateway is the network address of the home evolved base station connected to the local gateway;
  • the home evolved base station adds bearer information to the access request and sends it to the carrier core network;
  • the home evolved base station receives the create session request returned by the operator core network, and sends the create session request to the local gateway to complete the session creation between the local gateway and the operator core network, thereby implementing the local IP access service of the user terminal.
  • an embodiment of the present disclosure provides a management device for a local IP access service, including: a communication module and a processing module, where
  • the communication module is configured to receive an access request of the local IP access service sent by the user terminal;
  • the processing module is configured to obtain a network address of the local gateway, and generate bearer information of the local IP access service, where the network address of the local gateway is a network address of the home evolved base station connected to the local gateway, and the bearer information is added to the access request;
  • the communication module is further configured to send the access request processed by the processing module to the operator core network, receive the create session request returned by the operator core network, send the create session request to the local gateway, and complete the local gateway and the carrier core network.
  • the session is created to implement local IP access services of the user terminal.
  • an embodiment of the present disclosure further provides a home evolved base station, including a local IP access service management apparatus provided by an embodiment of the present disclosure.
  • the embodiment of the present disclosure further provides a local IP access service system, including a user terminal, a home evolved base station, a local gateway, and an operator core network, where the home evolved base station is configured to forward the local gateway and the carrier core. Communication data between networks.
  • an embodiment of the present disclosure further provides a non-transitory computer readable storage medium, where computer executable instructions are stored in a computer storage medium, and the computer executable instructions are used to execute the foregoing The management method of the local IP access service.
  • embodiments of the present disclosure also provide an electronic device including one or more processors, a memory, and one or more programs, the one or more programs being stored in a memory when being When a plurality of processors are executed, a management method of any one of the above-described local IP access services is performed.
  • An embodiment of the present disclosure provides a local IP access service management method, where the home evolved base station receives a create session request returned by the operator core network, and sends a create session request to the local gateway, where the local gateway and the carrier core can be completed.
  • the session creation of the network can implement the local IP access service of the user terminal, and provides a communication data between the LGW and the MME through the home evolved base station method, which can implement the arbitrary deployment of the LGW and simplify the LGW function, and can solve the problem.
  • the LGW deployment mode and location of the LIPA system are limited by the communication requirements between the LGW and the MME.
  • FIG. 2 is a flowchart of a LIPA management method according to a first embodiment of the present disclosure
  • FIG. 3 is a schematic structural diagram of a LIPA management apparatus according to a second embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of a keep-alive procedure according to a fourth embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of a LIPA request procedure according to a fourth embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a LIPA handover procedure according to a fourth embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of a proxy flow according to a fourth embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram showing the hardware structure of an electronic device according to a fifth embodiment of the present disclosure.
  • FIG. 1 is a flowchart of a LIPA management method according to a first embodiment of the present disclosure. As shown in FIG. 1, the LIPA management method provided in this embodiment includes S101-S104.
  • the home evolved base station receives an access request of a local IP access service sent by the user terminal;
  • the home evolved base station acquires a network address of the local gateway, and generates bearer information of the local IP access service, where the network address of the local gateway is a network address of the home evolved base station connected to the local gateway;
  • the home evolved base station adds the bearer information to the access request and sends the request to the operator core network.
  • the home evolved base station receives the create session request returned by the operator core network, sends the create session request to the local gateway, completes the session creation between the local gateway and the operator core network, and implements the local IP access service of the user terminal.
  • the LIPA management method in the foregoing embodiment may further include: before receiving the local IP access service request sent by the user terminal,
  • the home evolved base station periodically keeps alive with the local gateway
  • the local IP access service is enabled, and the local IP access service request sent by the user terminal is received;
  • the LIPA management method in the foregoing embodiment may further include:
  • the home evolved base station adds the network address of the home evolved base station to the keep-alive message, and sends the message to the local gateway, where the network address is set to trigger the local gateway to select the home evolved base station proxy;
  • the home evolved base station receives the keep-alive response of the local network, and the keep-alive response carries the network address of the home evolved base station that the local gateway selects as the proxy;
  • the home evolved base station saves the network address of the home evolved base station carried in the keep-alive response, and uses the network address of the home evolved base station as the network address of the local gateway.
  • the bearer information may further include a device identifier of the local gateway, and the LIPA management method in the foregoing embodiment may further include:
  • the home evolved base station receives a handover request of a local IP access service sent by the user terminal;
  • the home evolved base station transmits a handover request to the carrier core network
  • the home evolved base station receives the handover response returned by the operator core network, and completes the handover of the local IP access service.
  • the handover response is the device identifier of the local gateway sent by the source home evolved base station involved in the handover request of the operator core network, and the target home evolved. Sent when the device ID of the local gateway sent by the base station is the same.
  • the LIPA management method in the foregoing embodiment may further include:
  • the home evolved base station receives a handover request of a local IP access service sent by the user terminal;
  • the home evolved base station transmits a handover request to the carrier core network
  • the home evolved base station receives the handover response returned by the operator core network, and completes the handover of the local IP access service, where the handover response is the network address of the local gateway sent by the source home evolved base station involved in the handover request of the operator core network, and the target home evolved. Sent when the network address of the local gateway sent by the base station is the same.
  • the home evolved base station receives the create session request returned by the operator core network, and sends the create session request to the local gateway, which can complete the session creation between the local gateway and the operator core network, and can implement the local IP access service of the user terminal.
  • the home evolved base station method which can realize the arbitrary deployment of the LGW and the goal of simplifying the LGW function, and can solve the LGW deployment mode and location limitation of the LIPA system by LGW and MME. The problem of communication needs between.
  • the LIPA management apparatus may include: a communication module 21 and a processing module 22, where
  • the communication module 21 is configured to receive an access request of a local IP access service sent by the user terminal;
  • the processing module 22 is configured to obtain a network address of the local gateway, and generate bearer information of the local IP access service, where the network address of the local gateway is a network address of the home evolved base station connected to the local gateway, and the bearer information is added to the access request;
  • the communication module 21 is further configured to send the access request processed by the processing module to the operator core network, receive the create session request returned by the operator core network, send the create session request to the local gateway, and complete the local gateway and the carrier core network.
  • the session is created to implement local IP access services of the user terminal.
  • the communication module 21 in the foregoing embodiment is further configured to periodically keep alive with the local gateway; and the processing module is set to be successful in keeping alive.
  • the local IP access service is enabled. If the keepalive fails, the local IP access service is not enabled.
  • the processing module 22 in the foregoing embodiment is further configured to add a network address of the home evolved base station to the keep-alive message, and send the message to the local gateway through the communication module, where the network address is set to trigger the local gateway to select the home evolved base station proxy.
  • the processing module 22 in the foregoing embodiment is further configured to add a network address of the home evolved base station to the keep-alive message, and send the message to the local gateway through the communication module, where the network address is set to trigger the local gateway to select the home evolved base station proxy.
  • the keep-alive response carries the network address of the home evolved base station that the local gateway selects as the proxy, and saves the network address of the home evolved base station carried by the keep-alive response, and the network address of the home evolved base station The network address that is the local gateway.
  • the management device in the foregoing embodiment may further include switching.
  • the module 23 is configured to receive, by the communication module, a handover request of the local IP access service sent by the user terminal, send the handover request to the operator core network, receive the handover response returned by the operator core network, and complete the local IP access.
  • the handover response is sent when the network address of the local gateway sent by the source home evolved base station involved in the handover request is the same as the network address of the local gateway sent by the target home evolved base station.
  • the bearer information in the foregoing embodiment may further include a device identifier of the local gateway
  • the switching module 23 is further configured to receive, by using the communication module, a handover request of the local IP access service sent by the user terminal, and send the handover request to the
  • the carrier core network receives the handover response returned by the operator core network, and can complete the handover of the local IP access service.
  • the handover response is the device identifier of the local gateway sent by the source home evolved base station involved in the handover request of the operator core network, and Sent when the device ID of the local gateway sent by the target home evolved base station is the same.
  • all the functional modules involved in the foregoing embodiments may be implemented by an editable logic device that is burned into a specific software program, and may be implemented by a processor and a memory.
  • the embodiment of the present disclosure further provides a home evolved base station, including the LIPA management apparatus provided by the embodiment shown in FIG. 2.
  • the embodiment provides a local IP access service system, including a user terminal, a home evolved base station, a local gateway, and an operator core network, where the home evolved base station is configured to forward communication data between the local gateway and the carrier core network.
  • the user terminal in the foregoing embodiment is configured to send an access request of the local IP access service to the home eNodeB.
  • the eNodeB is configured to obtain the network address of the local gateway, and generate bearer information of the local IP access service.
  • the network address of the local gateway is the network address of the home evolved base station connected to the local gateway, and the bearer information is added to the access request, and the access request processed by the processing module is sent to the core network of the operator, and the return of the carrier core network is received.
  • Create a session request send a session request to the local gateway, complete the session creation between the local gateway and the carrier core network, and implement local IP access services of the user terminal.
  • the home evolved base station in the foregoing embodiment is configured to add a network address to the keep-alive message, and send the message to the local gateway, where the network address is set to trigger the local gateway to select the home evolved base station proxy, and receive the keep-alive response of the local network.
  • the keep-alive response carries the network address of the home evolved base station that is the proxy as the proxy, saves the network address of the home evolved base station carried in the keep-alive response, and uses the network address of the home evolved base station as the network address of the local gateway.
  • the user terminal in the foregoing embodiment is configured to send a handover request of the local IP access service to the home evolved base station;
  • the home evolved base station is configured to send the handover request to the operator core network, receive the handover response returned by the operator core network, and complete the handover of the local IP access service; the handover response is the source home evolved base station involved in the handover request by the operator core network.
  • the network address of the sent local gateway is sent when the network address of the local gateway sent by the target home evolved base station is the same;
  • the home evolved base station is configured to send the handover request to the operator core network, receive the handover response returned by the operator core network, and complete the handover of the local IP access service; the bearer information also includes the device identifier of the local gateway, and the handover response is the carrier core.
  • the network is sent when the device identifier of the local gateway sent by the source home evolved base station involved in the handover request is the same as the device identifier of the local gateway sent by the target home evolved base station.
  • This embodiment provides a LIPA enhancement solution, which can extend the deployment mode of the LGW under the LIPA technology, and can support the integrated deployment of the LGW and the AP, and can also support the independent deployment of the LGW, so as to satisfy the local offload data movement.
  • a LIPA enhancement solution which can extend the deployment mode of the LGW under the LIPA technology, and can support the integrated deployment of the LGW and the AP, and can also support the independent deployment of the LGW, so as to satisfy the local offload data movement.
  • sex we can balance the reliability and convenience of network deployment.
  • the L-GW exists as a local gateway hidden in the back end of the HeNB.
  • the communication between the L-GW and the EPC can be transited by the HeNB accessed by the UE as a routing device.
  • the UE is in the access process.
  • the INIT sends the LHN ID and the L-GW IP address to the MME, and the MME sends the L-GW IP address recommended by the HeNB as the S5 interface signaling sent by the MME to the L-GW.
  • the transit IP address of the data transmission is not limited to the data transmission.
  • the LHN ID carried in the HANDOVER NOTIFY and the PATH SWITCH REQUEST MESSAGE sent by the HeNB is used as the identifier of the UE accessing the local network resource, and the MME is based on the LHN ID or the IP address of the L-GW ( If there is no LHN ID, it is necessary to determine whether it belongs to the same campus and needs to switch across L-GW.
  • the method provided in this embodiment may include Step 1 - Step 3.
  • step 1 for the same L-GW, the same LHN ID is used to identify;
  • step 2 the external L-GW is connected to the S5 port of the core network through the S1 port of the base station;
  • step 3 when switching, the MME only needs to judge that the LHN ID is the same, that is, it is considered to be the same local LGW.
  • the UE initiates an access request of the campus APN, and the INITIAL sent by the HeNB1
  • the UPLINK NAS TRANSPORT can carry the LHN ID (optional) and the L-GW IP address at the same time.
  • the L-GW IP adopts the S1IP address of the HeNB1, and the same L-GW uses the same LHN ID to identify.
  • the MME carries the L-GW IP as a PGW IP address to the SGW.
  • the SGW sends the S5 interface message to the L-GW according to the PGW IP address recommended by the MME. Since the L-GW IP and the S1IP of the HeNB1 are the same, the S5 interface message is first forwarded to the HeNB1, and the HeNB1 receives the S5 interface sent by the SGW to the L-GW. After signaling, it is identified according to the message type that it needs to be forwarded to the LGW for NAT translation of the outer IP address, and the destination IP is translated into the L-GW's internal communication IP address L-GW@LN address, and the source IP is converted into the internal communication of HeNB1. After the IP address HeNB@LN address is sent to the L-GW, the channel of the S5 port is opened;
  • step 3 at the S1 handover, the handover decision of the LIPA connection is moved up to the MME implementation:
  • both the source HeNB1 and the target HeNB2 carry the LHN ID, whether the decision is a cross-L-GW handover according to whether the LHN ID is the same or not, regardless of whether the L-GW@IP address is the same;
  • the MME rejects the switching of the LIPA connection according to the capabilities of the base station (recommended LHN ID and L-GW@IP address), and completes the switching of the common public network connection.
  • the embodiment provides a LIPA implementation of the L-GW independent resident deployment by using the LIPA technology (L-GW built-in solution) specified by the protocol in the related technology, so as to meet the rapid deployment of the fast L-GW external solution. And the mobility requirements of LIPA's S1 switch.
  • EPC Evolved Packet Core, a packet core network, which is mainly composed of network elements such as MME, SGW, PGW, and PCRF
  • MME Mobile Management Entity
  • SGW Packet Data Network
  • PGW Packet Data Network
  • PCRF Packet Control Function
  • the keep-alive process is shown in FIG. 4 and may include S401-S404.
  • PDN public data network
  • S501-S511 may be included.
  • the UE performs an APN access request in the campus, and the UE initiates the requested PDN connection process by using a PDN connection request (Connectivity Request) of the NAS message.
  • PDN connection request Connectivity Request
  • the NAS message is sent to the MME through the Uplink NAS Transports of the H1 S1 message, the NAS message carries information related to the campus LIPA bearer such as the LHN ID and the L-GW@CN IP address, where the L-GW@CN IP address is equivalent.
  • the UE accesses the S1AP address of the HeNB.
  • the MME and the L-GW complete the session creation process, where the S5 port signaling sent by the MME to the L-GW can be forwarded by the HeNB;
  • the ECHO message between the MME and the L-GW may also be forwarded by the HeNB.
  • S601-S613 may be included.
  • the source side HeNB initiates a handover procedure, and sends a H0Reqest to the MME;
  • the MME performs the H0 decision.
  • the decision may be made according to whether the LHN ID is the same, regardless of whether the L-GW@IP address is the same; If the recorded source HeNB target HeNB has no LHN ID, the decision is made according to whether the L-GW@IP address is the same.
  • the target HeNB after receiving the H0Comfirm message sent by the UE, the target HeNB needs to notify the L-GW to switch the internal channel in addition to sending H0Notify to the MME. After the processing of the step ends, the downlink data received by the L-GW is sent to the target HeNB;
  • the L-GW in the campus can also select only one HeNB in the campus as the proxy of the L-GW to forward the S5 interface message.
  • the MME in the campus Only one L-GW can be seen. The MME only needs to release the LIPA connection and does not support the X2 and S1 handover restrictions to implement the L-GW external support and the LIPA handover scenario in the campus.
  • the process of the LGW selecting the proxy HeNB is as shown in FIG. 7 and may include S701-S709.
  • the L-GW in the campus can be kept on a regular basis.
  • the keep-alive message Echo Request carries the HeNB.
  • the S1AP address can be brought to the L-GW as the HeNB1@CN address;
  • the L-GW receives the IP address, detects whether the HeNB has been selected as a proxy for communication between the L-GW and the EPC, and when detecting that the HeNB is not selected as the proxy for communication between the L-GW and the EPC,
  • the HeNB@CN address carried by the HeNB1 can be recorded, and the HeNB@CN address is carried as an L-GW address in the Echo Response message to all HeNBs in the campus.
  • the accessed HeNB carries the L-GW address of the Echo Response message in the Uplink NAS Transports message to the MME.
  • the campus can also support multiple LGWs, and only need to carry the LHN ID and L-GW@CN IP address information in pairs in the messages INITIAL UE MESSAGE and UPLINK NAS TRANSPORT carried by the HeNB.
  • the embodiment of the present disclosure provides a local IP access service management method, where the home evolved base station receives a create session request returned by the operator core network, and sends a create session request to the local gateway to complete the local gateway and the carrier core network.
  • the session creation can implement the local IP access service of the user terminal, and provide a communication data between the LGW and the MME through the home evolved base station method, which can realize the arbitrary deployment of the LGW and simplify the LGW function, and can solve the LIPA system.
  • the LGW deployment method and location limitation are subject to the communication requirements between LGW and MME.
  • FIG. 8 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present disclosure. As shown in FIG. 9, the electronic device provided in this embodiment includes:
  • a processor 810 and a memory 820 may further include a communication interface 830 and a bus 840.
  • the processor 810, the memory 820, and the communication interface 830 can complete communication with each other through the bus 840.
  • Communication interface 830 can be used for information transfer.
  • the processor 810 can call the logic instructions in the memory 820 to perform the local IP access service implementation method of the above embodiment.
  • the logic instructions in the memory 820 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure.
  • the foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • a medium that can store program code, or a transitory storage medium including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • embodiments of the present disclosure can be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects. Moreover, the present disclosure may take the form of a computer program product embodied on one or more non-transitory computer readable storage media (which may include disk storage and optical storage, etc.) including computer usable program code.
  • 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.
  • the embodiments of the present disclosure provide a method, a device, and a home evolved base station for implementing a local IP access service, and the communication data between the LGW and the MME is forwarded by the home evolved base station method, so that the LGW can be deployed arbitrarily and the LGW function is simplified.

Landscapes

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

Abstract

一种本地IP接入业务实现方法及装置、系统、家庭演进基站，该方法包括：家庭演进基站接收用户终端发送的本地IP接入业务的接入请求；家庭演进基站获取本地网关的网络地址，生成本地IP接入业务的承载信息；家庭演进基站将承载信息添加到接入请求发送至运营商核心网；家庭演进基站接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，完成本地网关与运营商核心网的会话创建，实现用户终端的本地IP接入业务。

Description

本地IP接入业务实现方法及装置、系统、家庭演进基站 技术领域
本公开涉及通信领域，例如涉及一种本地IP接入业务实现方法及装置、系统、家庭演进基站。
背景技术
本地IP接入(Local IP Access，LIPA)业务主可用于独立的住宅或者企业网络(a single residential or Enterprise network)，第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)的协议提出的LIPA技术可以使用户的本地业务数据直接从本地(家庭/企业)的基站分流出去，一方面避免了IP数据流量迅速增加后对核心网的压力，另一方面还提高了IP数据包的路由效率。这样既减轻核心网络的负担，降低了运营商的核心网吞吐量和传输成本，还可以减少用户本地数据访问的数据传输时延。
LIPA技术是对家庭演进基站(Home evolved Node-B，HeNB)功能的增强，它可以允许终端通过HeNB直接访问本地网络内部的IP资源，通常用于运营商基于HeNB组建的本地业务服务。
3GPP的23.401协议提出了，使能LIPA的连接不支持切换(Hand Over，H0)：
A)在X2H0时移动管理实体(Mobile Management Entity，MME)收到路径切换请求消息(Path Switch Request message)，如果MME判断有LIPA连接没有被释放，MME会回复路径切换请求失败消息(Path Switch Request Failure message)给目标HeNB；
B)在S1H0时MME收到切换请求消息(Hand Over Request message)，如果MME判断有LIPA连接没有被释放，MME会回复切换失败消息(Hand Over Failure(Cause)message)给目标HeNB。
3GPP的23.859协议给出了LIPA的移动性提案，并给出了本地网关(Local Gateway，LGW)的选择和寻址方法，指出MME选择LGW可通过如下2种方法：
A)基于域名服务器(Domain Name Server，DNS)：LGW初始上电，向安全网关(Security Gateway，SeGW)获取到IP地址后，向DNS服务器进行注册，注册内容可以包括：LHN ID，L-GW@LN地址或者L-GW local完全合格域名/全称域名(Fully Qualified Domain Name，FQDN)，SeGW分配的L-GW@CN地址。MME 在收到用户设备(User Equipment，UE)的LIPA的公共数据网(Public Data Network，PDN)连接请求时，向DNS服务器发起DNS请求，DNS服务器返回符合条件的一个或多个LGW IP地址给MME；
B)基于居民接入网(Residential Access Network，RAN)：每个HeNB自身可以配置所有连接LGW的L-GW@LN地址或者FQDN。HeNB通过Sxx口获取到L-GW@CN地址。HeNB通过S1消息给MME上报L-GW@CN地址或者FQDNs。基于接入点名称(Access Point Name，APN)和LHN ID，核心网MME在HeNB提供的L-GW List里选择一个L-GW。
在3GPP标准制定过程中，最初的H(e)NB需求文稿(3GPPTS22.220)中只有LIPA的概念，应用场景是基于H(e)NB用户，业务可以是家庭/企业网的业务，也可以是Internet网业务。但是明确了对宏网络中的Internet业务进行分流的需求以后，SIPTO概念随之提出。3GPP的R12协议对LIPA的移动性和本地网络的SIPTO技术合一，统称为LIMONET。
对于支持SIPTO驻地独立部署方式，R12协议明确规定，服务网关(Serving Gateway，SGW)下沉到本地，并与L-GW合一，HeNB在初始化用户设备消息(initial UE message)，上行非接入层传输(uplink(Non-Acess Stratum)NAS transport)，切换通知(handover notify)和and路径切换请求消息(path switch request message)携带LHN ID给MME，MME在源HeNB和目标HeNB的LHN ID相同的情况下，支持带SIPTO的切换。R12协议可以规定：从业务的形式来看，LIPA用于H(e)NB内的业务，而SIPTO用于公网的业务；从网络架构来说，LIPA用于H(e)NB，而SIPTO可用于H(e)NB，也可用于宏网络。
如图1所示，相关技术的使用IP数据分流(Selected IP Traffic Offload，SIPTO)的L-GW外置驻地部署方案也存在一定的缺陷，包括：
1)影响公网流量，公网数据需要从L-SGW(local sgw)到R-PGW(remote pgw)；
2)终端的业务服务依赖于S1-C，S5，AP-LGW这三段接口的通讯保障，任何链路的异常都会导致终端的掉话，网络维护复杂；
3)LGW作为独立网元部署时，需要实现S11/S5口的通讯，由于LGW驻地化部署，因此需要解决接入资源的问题，如果采用专线接入，则对传输资源依赖较大，且为了安全考虑需要专用机房。如果采用共享传输资源接入，为了保证安全性需要LGW支持网络接入所需的各类传输协议和安全协议，比如IPSec，网络管理和部署均十分不便。
综上，相关技术中的LIPA系统的LGW部署方式及位置受限受制于LGW与MME之间的通信需求，灵活性不高，且要求LGW支持网络接入所需的各类传输协议和安全协议。
发明内容
本公开提供了一种本地IP接入业务实现方法及装置、系统、家庭演进基站，可以解决LIPA系统的LGW部署方式及位置受限受制于LGW与MME之间的通信需求的问题。
一方面，本公开实施例提供了一种本地IP接入业务的管理方法，包括：
家庭演进基站接收用户终端发送的本地IP接入业务的接入请求；
家庭演进基站获取本地网关的网络地址，生成本地IP接入业务的承载信息，本地网关的网络地址为与本地网关连接的家庭演进基站的网络地址；
家庭演进基站将承载信息添加到接入请求发送至运营商核心网；以及
家庭演进基站接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，完成本地网关与运营商核心网的会话创建，实现用户终端的本地IP接入业务。
另一方面，本公开实施例提供了一种本地IP接入业务的管理装置，包括：通信模块及处理模块，其中，
通信模块设置为接收用户终端发送的本地IP接入业务的接入请求；
处理模块设置为获取本地网关的网络地址，生成本地IP接入业务的承载信息，本地网关的网络地址为与本地网关连接的家庭演进基站的网络地址，将承载信息添加到接入请求；
通信模块还设置为将处理模块处理后的接入请求发送至运营商核心网，接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，完成本地网关与运营商核心网的会话创建，实现用户终端的本地IP接入业务。
另一方面，本公开实施例还提供了一种家庭演进基站，包括本公开实施例提供的本地IP接入业务的管理装置。
另一方面，本公开实施例还提供了一种本地IP接入业务系统，包括用户终端、家庭演进基站、本地网关及运营商核心网，其中，家庭演进基站设置为转发本地网关与运营商核心网之间的通信数据。
另一方面，本公开实施例还提供了一种非暂态计算机可读存储介质，计算机存储介质中存储有计算机可执行指令，计算机可执行指令用于执行前述的本 地IP接入业务的管理方法。
另一方面，本公开实施例还提供一种电子设备，该电子设备包括一个或多个处理器、存储器以及一个或多个程序，所述一个或多个程序存储在存储器中，当被一个或多个处理器执行时，执行上述任意一种本地IP接入业务的管理方法。
本公开实施例提供了一种本地IP接入业务管理方法，该方法通过家庭演进基站接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，可以完成本地网关与运营商核心网的会话创建，可以实现用户终端的本地IP接入业务，提供了一种通过家庭演进基站法转发LGW与MME之间的通信数据，可以实现LGW的任意部署及简化LGW功能的目标，可以解决LIPA系统的LGW部署方式及位置受限受制于LGW与MME之间的通信需求的问题。
附图说明
图1为相关技术中的LGW部署示意图；
图2为本公开第一实施例提供的LIPA管理方法的流程图；
图3为本公开第二实施例提供的LIPA管理装置的结构示意图；
图4是本公开第四实施例涉及的保活流程的示意图；
图5是本公开第四实施例涉及的LIPA请求流程的示意图；
图6是本公开第四实施例涉及的LIPA切换流程的示意图；
图7是本公开第四实施例涉及的代理流程的示意图；以及
图8是本公开第五实施例涉及的电子设备的硬件结构示意图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行相关描述。所描述的实施例只是本公开中一部分实施例，而不是全部的实施例。此外，在不冲突的情况下，以下实施例和实施例中的特征可以相互组合。
第一实施例
图1为本公开第一实施例提供的LIPA管理方法的流程图，由图1可知，本实施例提供的LIPA管理方法包括S101-S104。
在S101中，家庭演进基站接收用户终端发送的本地IP接入业务的接入请求；
在S102中，家庭演进基站获取本地网关的网络地址，生成本地IP接入业务的承载信息，本地网关的网络地址为与本地网关连接的家庭演进基站的网络地址；
在S103中，家庭演进基站将承载信息添加到接入请求发送至运营商核心网；
在S104中，家庭演进基站接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，完成本地网关与运营商核心网的会话创建，可以实现用户终端的本地IP接入业务。
在一些实施例中，当家庭演进基站支持本地IP接入业务、本地网关独立部署，上述实施例中的LIPA管理方法在接收用户终端发送的本地IP接入业务请求之前，还可以包括：
家庭演进基站周期性与本地网关进行保活；
当保活成功，则使能本地IP接入业务，接收用户终端发送的本地IP接入业务请求；以及
当保活失败，则不使能本地IP接入业务。
在一些实施例中，上述实施例中的LIPA管理方法还可以包括：
家庭演进基站将该家庭演进基站的网络地址添加到保活消息，发送至本地网关，网络地址设置为触发本地网关选择家庭演进基站代理；
家庭演进基站接收本地网络的保活响应，保活响应携带本地网关选择作为代理的家庭演进基站的网络地址；以及
家庭演进基站保存保活响应携带的家庭演进基站的网络地址，将该家庭演进基站的网络地址作为本地网关的网络地址。
在一些实施例中，承载信息还可以包括本地网关的设备标识，上述实施例中的LIPA管理方法还可以包括：
家庭演进基站接收用户终端发送的本地IP接入业务的切换请求；
家庭演进基站将切换请求发送至运营商核心网；以及
家庭演进基站接收运营商核心网返回的切换响应，完成本地IP接入业务的切换，切换响应为运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的设备标识、与目标家庭演进基站发送的本地网关的设备标识相同时发送的。
在一些实施例中，上述实施例中的LIPA管理方法还可以包括：
家庭演进基站接收用户终端发送的本地IP接入业务的切换请求；
家庭演进基站将切换请求发送至运营商核心网；以及
家庭演进基站接收运营商核心网返回的切换响应，完成本地IP接入业务的切换，切换响应为运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的网络地址、与目标家庭演进基站发送的本地网关的网络地址相同时发送的。
本实施例通过家庭演进基站接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，可以完成本地网关与运营商核心网的会话创建，可以实现用户终端的本地IP接入业务，提供了一种通过家庭演进基站法转发LGW与MME之间的通信数据，可以实现LGW的任意部署及简化LGW功能的目标，可以解决LIPA系统的LGW部署方式及位置受限受制于LGW与MME之间的通信需求的问题。
第二实施例
图2为本公开第二实施例提供的LIPA管理装置的结构示意图，由图2可知，本实施例提供的LIPA管理装置可以包括：通信模块21及处理模块22，其中，
通信模块21设置为接收用户终端发送的本地IP接入业务的接入请求；
处理模块22设置为获取本地网关的网络地址，生成本地IP接入业务的承载信息，本地网关的网络地址为与本地网关连接的家庭演进基站的网络地址，将承载信息添加到接入请求；
通信模块21还设置为将处理模块处理后的接入请求发送至运营商核心网，接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，完成本地网关与运营商核心网的会话创建，实现用户终端的本地IP接入业务。
在一些实施例中，当家庭演进基站支持本地IP接入业务、本地网关独立部署，上述实施例中的通信模块21还设置为周期性与本地网关进行保活；处理模块设置为当保活成功，则使能本地IP接入业务，当保活失败，则不使能本地IP接入业务。
在一些实施例中，上述实施例中的处理模块22还设置为将家庭演进基站的网络地址添加到保活消息，通过通信模块发送至本地网关，网络地址设置为触发本地网关选择家庭演进基站代理，通过通信模块接收本地网络的保活响应，保活响应携带本地网关选择作为代理的家庭演进基站的网络地址，保存保活响应携带的家庭演进基站的网络地址，将该家庭演进基站的网络地址作为本地网关的网络地址。
如图2所示，在一些实施例中，上述实施例中的管理装置还可以包括切换 模块23，切换模块23设置为通过通信模块接收用户终端发送的本地IP接入业务的切换请求，将切换请求发送至运营商核心网，接收运营商核心网返回的切换响应，完成本地IP接入业务的切换，切换响应为运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的网络地址、与目标家庭演进基站发送的本地网关的网络地址相同时发送的。
在一些实施例中，上述实施例中的承载信息还可以包括本地网关的设备标识，切换模块23还设置为通过通信模块接收用户终端发送的本地IP接入业务的切换请求，将切换请求发送至运营商核心网，接收运营商核心网返回的切换响应，可以完成本地IP接入业务的切换，切换响应为运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的设备标识、与目标家庭演进基站发送的本地网关的设备标识相同时发送的。
在实际应用中，上述实施例涉及的所有功能模块都可以由烧入有特定软件程序的可编辑逻辑器件实现，可以有处理器与存储器相互配合实现。
本公开实施例还提供了一种家庭演进基站，包括图2所示实施例提供的LIPA管理装置。
第三实施例
本实施例提供了一种本地IP接入业务系统，包括用户终端、家庭演进基站、本地网关及运营商核心网，其中，家庭演进基站设置为转发本地网关与运营商核心网之间的通信数据。
可选地，上述实施例中的用户终端设置为向家庭演进基站发送本地IP接入业务的接入请求；家庭演进基站设置为获取本地网关的网络地址，生成本地IP接入业务的承载信息，本地网关的网络地址为与本地网关连接的家庭演进基站的网络地址，将承载信息添加到接入请求，将处理模块处理后的接入请求发送至运营商核心网，接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，完成本地网关与运营商核心网的会话创建，实现用户终端的本地IP接入业务。
可选地，上述实施例中的家庭演进基站设置为将其网络地址添加到保活消息，发送至本地网关，网络地址设置为触发本地网关选择家庭演进基站代理，接收本地网络的保活响应，保活响应携带本地网关选择作为代理的家庭演进基站的网络地址，保存保活响应携带的家庭演进基站的网络地址，将该家庭演进基站的网络地址作为本地网关的网络地址。
可选地，上述实施例中的用户终端设置为向家庭演进基站发送本地IP接入业务的切换请求；
家庭演进基站设置为将切换请求发送至运营商核心网，接收运营商核心网返回的切换响应，完成本地IP接入业务的切换；切换响应为运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的网络地址、与目标家庭演进基站发送的本地网关的网络地址相同时发送的；
或者，
家庭演进基站设置为将切换请求发送至运营商核心网，接收运营商核心网返回的切换响应，完成本地IP接入业务的切换；承载信息还包括本地网关的设备标识，切换响应为运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的设备标识、与目标家庭演进基站发送的本地网关的设备标识相同时发送的。
第四实施例
现结合具体应用场景对本发明做进一步的诠释说明。本实施例提供一种LIPA增强方案，该方案可以对LIPA技术下LGW的部署方式进行扩展，既可以支持LGW和AP的合一部署，也可以支持LGW的独立部署，这样在满足本地分流数据移动性的基础上，可以兼顾网络部署可靠性和便利性问题。
L-GW作为隐藏在HeNB后端的一个本地网关存在，所有L-GW与EPC之间的通讯都可以通过UE接入的HeNB作为路由设备，进行中转；可选地，UE在接入流程中，HeNB向MME发送的INITIAL UE MESSAGE，UPLINK NAS TRANSPORT里同时携带LHN ID和L-GW IP地址给MME，MME根据HeNB推荐上来的L-GW IP地址作为MME发给L-GW的S5口信令和数据发送的中转IP地址，在UE发送切换时，HeNB发送的HANDOVER NOTIFY和PATH SWITCH REQUEST MESSAGE里携带的LHN ID作为UE接入本地网络资源的标识，MME根据LHN ID或者L-GW的IP地址(未带LHN ID的情况下)来判断是否属于同一个园区需要进行跨L-GW的切换。
本实施例提供的方法可以包括步骤1-步骤3。
在步骤1中，对于同一个L-GW，采用相同的LHN ID来标识；
在步骤2中，外置L-GW与核心网的S5口连接通过基站的S1口传输；
在步骤3中，切换时，MME只需要判断LHN ID相同，即认为是同一个本地LGW。
可选地，在步骤1中，UE发起园区APN的接入请求，HeNB1发送的INITIAL  UE MESSAGE，UPLINK NAS TRANSPORT里可以同时携带LHN ID(可选)和L-GW IP地址，其中L-GW IP采用HeNB1的S1IP地址，对于同一个L-GW，采用相同的LHN ID来标识。
在步骤2中，MME将L-GW IP作为PGW IP地址携带给SGW。SGW根据MME推荐的PGW IP地址发送S5口消息给L-GW，由于L-GW IP和HeNB1的S1IP相同，因此S5口消息首先被转发给HeNB1，HeNB1收到SGW发送给L-GW的S5口信令后，根据消息类型识别出需要转发给LGW，进行外层IP地址的NAT转换，目的IP转换成L-GW的内部通讯IP地址L-GW@LN地址，源IP转换成HeNB1的内部通讯IP地址HeNB@LN地址后，发送给L-GW，打通S5口的通道；
在步骤3中，在S1切换时，LIPA连接的切换判决上移到MME实现：
当源HeNB1和目标HeNB2都携带有LHN ID时，则根据LHN ID是否相同进行判决是否为跨L-GW切换，不考虑L-GW@IP地址是否相同；
当源HeNB1和目标HeNB2有一方没带有LHN ID时，则根据L-GW@IP地址是否相同进行判决是否为跨L-GW切换；
当源HeNB1和目标HeNB2携带的LHN ID(HANDOVER NOTIFY携带)不同时，则按照跨LGW切换来处理；
当UE从园区内移动到园区外，MME根据基站的能力(推荐的LHN ID和L-GW@IP地址)，拒绝LIPA连接的切换，并完成普通公网连接的切换。
本实施例提供了一种利用相关技术中协议规定的LIPA技术(L-GW内置方案)，来完成L-GW独立的驻地部署的LIPA实现，从而可以满足快速L-GW外置方案的快速部署和LIPA的S1切换的移动性需求。
对于EPC(Evolved Packet Core，分组核心网，主要由MME、SGW、PGW、PCRF等网元构成)收到LHN ID和LGW@IP的场景，在该种场景下，园区内MME的处理基本和L-GW内置相同，无需另外拉线部署，MME可以只需要增加S1口的切换判决条件，及放开LIPA连接不支持X2和S1切换的限制就可以实现支持L-GW外置及园区内带LIPA的切换场景。
1、HeNB和LGW的保活流程，H(e)NB正常上电后由H(e)NB向L-GW发送Echo request消息进行保活。
保活流程如图4所示，可以包括S401-S404。
在S401-S402中，园区内HeNB1上电完成后，当LIPA使能，且为L-GW独立部署方式，则定期向园区内的L-GW进行保活：
当成功收到L-GW回复的Echo Response时，HeNB1使能LIPA；
当未能成功收到L-GW回复的Echo Response时，HeNB1不使能LIPA；
在S403-S404中，HeNB2上电完成后和L-GW的握手，定期向园区内的L-GW进行保活：
当成功收到L-GW回复的Echo Response时，HeNB2使能LIPA；
当未能成功收到L-GW回复的Echo Response时，HeNB2不使能LIPA。
2、UE请求的公用数据网(Public Data Network，PDN)connectivity流程。
如图5所示，可以包括S501-S511。
在S501中，UE在园区内进行APN的接入请求，UE通过NAS消息的PDN连接请求(Connectivity Request)发起请求的PDN连接过程。该NAS消息通过HeNB的S1消息的Uplink NAS Transports发送到MME时，该NAS消息携带LHN ID和L-GW@CN IP地址等园区LIPA承载相关的信息，其中，L-GW@CN IP地址相当于UE接入HeNB的S1AP地址。
在S502-S505中，MME和L-GW完成创建会话过程，其中，MME发给L-GW的S5口信令都可以通过HeNB进行转发的；
在S506-S507中，UE完成接入；
在S508-S511中，MME和L-GW之间的ECHO消息也可以通过HeNB进行转发。
3、园区内的S1H0切换流程。
如图6所示，可以包括S601-S613。
在S601-S602中，源侧HeNB发起切换过程，给MME发送H0Reqest；
在S603中，MME做H0判决，对于LIPA承载，当MME记录的源HeNB目标HeNB都带有LHN ID，则可以根据LHN ID是否相同进行判决，不考虑L-GW@IP地址是否相同；当MME记录的源HeNB目标HeNB有一方没带有LHN ID，则根据L-GW@IP地址是否相同进行判决；
在S604-S609中，S1H0的其他流程，此时，LGW收到的下行数据依然发送到源HeNB；
在S610-S611中，目标HeNB收到UE发送的H0Comfirm消息后，除了给MME发送H0Notify外，还需要通知L-GW切换内部通道。该步骤处理结束后，L-GW收到的下行数据发送给目标HeNB；
在S612-S613中，源侧完成释放流程。
对于EPC只收到LGW@IP的场景，园区内L-GW也可以只选择园区内的其中一个HeNB作为L-GW的代理进行S5口消息的转发，在该种场景下，园区内MME 可见的只有1个L-GW，MME只需要放开LIPA连接不支持X2和S1切换的限制就可以实现支持L-GW外置及及园区内带LIPA的切换场景。
可选地，LGW选择代理HeNB的流程如图7所示，可以包括S701-S709。
在S701中，园区内HeNB1上电完成后，当LIPA使能，且为L-GW独立部署方式，则可以定期向园区内的L-GW进行保活，其中，保活消息Echo Request里携带HeNB的S1AP地址可以作为HeNB1@CN地址带给L-GW；
在S702-S705中，L-GW收到该IP地址，检测是否已经选择了HeNB作为L-GW与EPC之间通信的代理，当检测没有选择HeNB作为L-GW与EPC之间通信的代理时，可以记录HeNB1携带的HeNB@CN地址，并将该HeNB@CN地址作为L-GW地址在Echo Response消息中携带给园区内的所有HeNB。当UE接入时，接入的HeNB在Uplink NAS Transports消息中携带Echo Response消息中细带的L-GW地址给MME。
在S706-S709中，当L-GW选择了HeNB1作为L-GW与EPC通信代理后，就启动定时器进行等待，如果定时器超时，仍然不见HeNB1再次发送握手消息，则认为HeNB1掉电。L-GW需要将该L-GW的状态更新为未选择代理状态，并需要重复S702-S705进行代理的选择和更新。
在实际应用中，园区也可以支持多个LGW，只需要在HeNB携带的消息INITIAL UE MESSAGE，UPLINK NAS TRANSPORT中，成对的携带LHN ID和L-GW@CN IP地址信息。
本公开实施例提供了一种本地IP接入业务管理方法，该方法通过家庭演进基站接收运营商核心网返回的创建会话请求，将创建会话请求发送至本地网关，完成本地网关与运营商核心网的会话创建，可以实现用户终端的本地IP接入业务，提供一种通过家庭演进基站法转发LGW与MME之间的通信数据，可以实现LGW的任意部署及简化LGW功能的目标，可以解决LIPA系统的LGW部署方式及位置受限受制于LGW与MME之间的通信需求的问题。
第五实施例
图8为本公开实施例提供了一种电子设备的硬件结构示意图，由图9可知，本实施例提供的电子设备包括：
处理器(processor)810和存储器(memory)820；还可以包括通信接口(Communications Interface)830和总线840。
其中，处理器810、存储器820和通信接口830可以通过总线840完成相互间的通信。通信接口830可以用于信息传输。处理器810可以调用存储器820中的逻辑指令，以执行上述实施例的本地IP接入业务实现方法。
此外，上述的存储器820中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质，也可以是暂态存储介质。
本领域内的技术人员应明白，本公开实施例可提供为方法、系统、或计算机程序产品。因此，本公开可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开可采用在一个或多个包含有计算机可用程序代码的非暂态计算机可读存储介质(可以包括磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个 流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
工业实用性
本公开实施例提供了本地IP接入业务实现方法及装置、系统、家庭演进基站，通过家庭演进基站法转发LGW与MME之间的通信数据，可以实现LGW的任意部署及简化LGW功能的目标。

Claims (16)

  1. 一种本地IP接入业务的管理方法，包括：
    家庭演进基站接收用户终端发送的本地IP接入业务的接入请求；
    家庭演进基站获取本地网关的网络地址，生成本地IP接入业务的承载信息，所述本地网关的网络地址为与所述本地网关连接的家庭演进基站的网络地址；
    家庭演进基站将所述承载信息添加到所述接入请求发送至运营商核心网；以及
    家庭演进基站接收所述运营商核心网返回的创建会话请求，将所述创建会话请求发送至所述本地网关，完成所述本地网关与所述运营商核心网的会话创建，实现所述用户终端的本地IP接入业务。
  2. 如权利要求1所述的方法，当家庭演进基站支持本地IP接入业务、所述本地网关独立部署时，所述管理方法在接收用户终端发送的本地IP接入业务请求之前，还包括：
    家庭演进基站周期性与所述本地网关进行保活；
    当保活成功，则使能本地IP接入业务，接收用户终端发送的本地IP接入业务请求；以及
    当保活失败，则不使能本地IP接入业务。
  3. 如权利要求2所述的方法，还包括：
    家庭演进基站将所述家庭演进基站网络地址添加到保活消息，发送至本地网关，所述网络地址设置为触发本地网关选择家庭演进基站代理；
    家庭演进基站接收本地网络的保活响应，所述保活响应携带所述本地网关选择作为代理的家庭演进基站的网络地址；以及
    家庭演进基站保存所述保活响应携带的家庭演进基站的网络地址，将所述家庭演进基站的网络地址作为所述本地网关的网络地址。
  4. 如权利要求1至3任一项所述的方法，所述承载信息还包括本地网关的设备标识，所述管理方法还包括：
    家庭演进基站接收用户终端发送的本地IP接入业务的切换请求；
    家庭演进基站将所述切换请求发送至运营商核心网；以及
    家庭演进基站接收所述运营商核心网返回的切换响应，完成本地IP接入业务的切换，所述切换响应为所述运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的设备标识、与目标家庭演进基站发送的本地网关的设备标识相同时发送的。
  5. 如权利要求1至3任一项所述的方法，还包括：
    家庭演进基站接收用户终端发送的本地IP接入业务的切换请求；
    家庭演进基站将所述切换请求发送至运营商核心网；以及
    家庭演进基站接收所述运营商核心网返回的切换响应，完成本地IP接入业务的切换，所述切换响应为所述运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的网络地址、与目标家庭演进基站发送的本地网关的网络地址相同时发送的。
  6. 一种本地IP接入业务的管理装置，包括：通信模块及处理模块，其中，
    所述通信模块设置为接收用户终端发送的本地IP接入业务的接入请求；
    所述处理模块设置为获取本地网关的网络地址，生成本地IP接入业务的承载信息，所述本地网关的网络地址为与所述本地网关连接的家庭演进基站的网络地址，将所述承载信息添加到所述接入请求；以及
    所述通信模块还设置为将所述处理模块处理后的接入请求发送至运营商核心网，接收所述运营商核心网返回的创建会话请求，将所述创建会话请求发送至所述本地网关，完成所述本地网关与所述运营商核心网的会话创建，实现所述用户终端的本地IP接入业务。
  7. 如权利要求6所述的装置，其中，当家庭演进基站支持本地IP接入业务、所述本地网关独立部署，所述通信模块还设置为周期性与所述本地网关进行保活；所述处理模块设置为当保活成功，则使能本地IP接入业务，当保活失败，则不使能本地IP接入业务。
  8. 如权利要求7所述的装置，其中，所述处理模块还设置为将家庭演进基站的网络地址添加到保活消息，通过所述通信模块发送至本地网关，所述网络地址设置为触发本地网关选择家庭演进基站代理，通过所述通信模块接收本地网络的保活响应，所述保活响应携带所述本地网关选择作为代理的家庭演进基站的网络地址，保存所述保活响应携带的家庭演进基站的网络地址，将所述家庭演进基站的网络地址作为所述本地网关的网络地址。
  9. 如权利要求6至8任一项所述的装置，还包括切换模块，所述切换模块设置为通过所述通信模块接收用户终端发送的本地IP接入业务的切换请求，将所述切换请求发送至运营商核心网，接收所述运营商核心网返回的切换响应，完成本地IP接入业务的切换，所述切换响应为所述运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的网络地址、与目标家庭演进基站发送的本地网关的网络地址相同时发送的。
  10. 如权利要求9所述的装置，其中，所述承载信息还包括本地网关的设备标识，所述切换模块还设置为通过所述通信模块接收用户终端发送的本地IP接入业务的切换请求，将所述切换请求发送至运营商核心网，接收所述运营商核心网返回的切换响应，完成本地IP接入业务的切换，所述切换响应为所述运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的设备标识、与目标家庭演进基站发送的本地网关的设备标识相同时发送的。
  11. 一种家庭演进基站，包括如权利要求6至10任一项所述的本地IP接入业务的管理装置。
  12. 一种本地IP接入业务系统，包括用户终端、家庭演进基站、本地网关及运营商核心网，其中，所述家庭演进基站设置为转发所述本地网关与所述运营商核心网之间的通信数据。
  13. 如权利要求12所述的系统，其中，
    所述用户终端设置为向所述家庭演进基站发送本地IP接入业务的接入请求；以及
    所述家庭演进基站设置为获取所述本地网关的网络地址，生成本地IP接入业务的承载信息，所述本地网关的网络地址为与所述本地网关连接的家庭演进基站的网络地址，将所述承载信息添加到所述接入请求，将所述处理模块处理后的接入请求发送至所述运营商核心网，接收所述运营商核心网返回的创建会话请求，将所述创建会话请求发送至所述本地网关，完成所述本地网关与所述运营商核心网的会话创建，实现所述用户终端的本地IP接入业务。
  14. 如权利要求12所述的系统，其特中，所述家庭演进基站设置为将所述家庭演进基站的网络地址添加到保活消息，发送至本地网关，所述网络地址设置为触发本地网关选择家庭演进基站代理，接收本地网络的保活响应，所述保活响应携带所述本地网关选择作为代理的家庭演进基站的网络地址，保存所述保活响应携带的家庭演进基站的网络地址，将所述家庭演进基站的网络地址作为所述本地网关的网络地址。
  15. 如权利要求12至14任一项所述的系统，其中，
    所述用户终端设置为向所述家庭演进基站发送本地IP接入业务的切换请求；
    所述家庭演进基站设置为将所述切换请求发送至运营商核心网，接收所述运营商核心网返回的切换响应，完成本地IP接入业务的切换；所述切换响应为所述运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的网络地 址、与目标家庭演进基站发送的本地网关的网络地址相同时发送的；或者
    所述家庭演进基站设置为将所述切换请求发送至运营商核心网，接收所述运营商核心网返回的切换响应，完成本地IP接入业务的切换；所述承载信息还包括本地网关的设备标识，所述切换响应为所述运营商核心网在切换请求涉及的源家庭演进基站发送的本地网关的设备标识、与目标家庭演进基站发送的本地网关的设备标识相同时发送的。
  16. 一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-5任一项的本地IP接入业务的管理方法。
PCT/CN2016/101629 2016-06-30 2016-10-10 本地ip接入业务实现方法及装置、系统、家庭演进基站 WO2018000654A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610512578.4A CN108307521A (zh) 2016-06-30 2016-06-30 本地ip接入业务实现方法及装置、系统、家庭演进基站
CN201610512578.4 2016-06-30

Publications (1)

Publication Number Publication Date
WO2018000654A1 true WO2018000654A1 (zh) 2018-01-04

Family

ID=60785852

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/101629 WO2018000654A1 (zh) 2016-06-30 2016-10-10 本地ip接入业务实现方法及装置、系统、家庭演进基站

Country Status (2)

Country Link
CN (1) CN108307521A (zh)
WO (1) WO2018000654A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114938342A (zh) * 2022-01-27 2022-08-23 浙江浩瀚能源科技有限公司 一种可远程触发本地ui自动化测试及监控方法
CN115460614A (zh) * 2022-08-30 2022-12-09 中国船舶集团有限公司第七一六研究所 一种采用级联方式的便携式可扩展5g系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112654100B9 (zh) 2019-10-10 2023-11-03 中国移动通信有限公司研究院 一种信息处理方法和相关网络设备
CN112954630B (zh) * 2021-02-08 2023-11-14 浪潮通信技术有限公司 一种基于5g端计算网关业务保活的方法
CN114584387B (zh) * 2022-03-11 2024-07-19 深圳明心科技有限公司 一种5g上网行为管理方法、装置及5g网关

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102131291A (zh) * 2010-01-13 2011-07-20 中兴通讯股份有限公司 本地接入网关获取终端的寻呼信息的方法和系统
CN102905329A (zh) * 2011-07-29 2013-01-30 北京三星通信技术研究有限公司 一种支持切换的方法
CN103391330A (zh) * 2012-05-11 2013-11-13 中兴通讯股份有限公司 本地网关的ip地址分配方法、中继节点及分组数据网关
US20140029579A1 (en) * 2011-05-16 2014-01-30 Samsung Electronics Co. Ltd. Method and device for determining continuous session support during support of limonet in mobile communication system
CN105282724A (zh) * 2014-07-21 2016-01-27 中兴通讯股份有限公司 一种本地因特网协议接入会话的识别方法、设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102131291A (zh) * 2010-01-13 2011-07-20 中兴通讯股份有限公司 本地接入网关获取终端的寻呼信息的方法和系统
US20140029579A1 (en) * 2011-05-16 2014-01-30 Samsung Electronics Co. Ltd. Method and device for determining continuous session support during support of limonet in mobile communication system
CN102905329A (zh) * 2011-07-29 2013-01-30 北京三星通信技术研究有限公司 一种支持切换的方法
CN103391330A (zh) * 2012-05-11 2013-11-13 中兴通讯股份有限公司 本地网关的ip地址分配方法、中继节点及分组数据网关
CN105282724A (zh) * 2014-07-21 2016-01-27 中兴通讯股份有限公司 一种本地因特网协议接入会话的识别方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Dual Connectivity and SIPT0@LN with Stand-Alone GW", 3GPP TSG-RAN WG3 #87BIS R3-150745, 24 April 2015 (2015-04-24), XP050937356 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114938342A (zh) * 2022-01-27 2022-08-23 浙江浩瀚能源科技有限公司 一种可远程触发本地ui自动化测试及监控方法
CN115460614A (zh) * 2022-08-30 2022-12-09 中国船舶集团有限公司第七一六研究所 一种采用级联方式的便携式可扩展5g系统

Also Published As

Publication number Publication date
CN108307521A (zh) 2018-07-20

Similar Documents

Publication Publication Date Title
US11026080B2 (en) Policy control function determining method, apparatus, and system
KR101478418B1 (ko) 하이브리드 네트워크에서 통합 게이트웨이에 대한 확장형 로컬 ｉｐ 액세스
US10098042B2 (en) MME, local server, MME-local server interface, and data transmission method for optimized data path in LTE network
WO2018000654A1 (zh) 本地ip接入业务实现方法及装置、系统、家庭演进基站
JP2018160941A (ja) ホーム基地局及びマクロ基地局
KR102469973B1 (ko) 통신 방법 및 장치
US8909223B2 (en) Multicast optimization and aggregation in an enterprise controller
US9572194B2 (en) Method and device for determining continuous session support during support of LIMONET in mobile communication system
WO2019185062A1 (zh) 一种通信方法及装置
US20150271725A1 (en) Method and apparatus for handover between content servers for transmission path optimization
JP2019521588A (ja) 通信制御方法および関連するネットワーク要素
BR112020003137A2 (pt) métodos e aparelhos para evitar tempestade de paginação durante difusão de arp para pdu tipo ethernet
EP2932782B1 (en) A new architecture for cellular networks
EP4115595B1 (en) Application triggered setup of distributed anchor for edge computing
JP5904206B2 (ja) 通信システム、通信方法及び通信プログラム
EP3410752A1 (en) Mobility management method, apparatus and system
WO2019037500A1 (zh) 一种选择无线接入网设备的方法及装置
WO2013053133A1 (zh) 业务数据传输处理方法、设备以及通信系统
JP2024123131A (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
US20240098148A1 (en) Restoration of a pdn connection at pgw failure
CN106797632B (zh) 实现业务连续性的方法、装置及系统
WO2023185352A1 (zh) 基于无线网络的数据处理方法及系统
WO2016101616A1 (zh) 园区业务访问的方法、装置及系统
WO2012152226A1 (zh) 数据传输的方法、无线接入网设备和通信系统
US20210219261A1 (en) Techniques for supporting user equipment paging in an enterprise fabric

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: 16907050

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16907050

Country of ref document: EP

Kind code of ref document: A1