WO2013107057A1 - 一种服务请求sr流程的执行方法、装置及服务网关 - Google Patents

一种服务请求sr流程的执行方法、装置及服务网关 Download PDF

Info

Publication number
WO2013107057A1
WO2013107057A1 PCT/CN2012/070704 CN2012070704W WO2013107057A1 WO 2013107057 A1 WO2013107057 A1 WO 2013107057A1 CN 2012070704 W CN2012070704 W CN 2012070704W WO 2013107057 A1 WO2013107057 A1 WO 2013107057A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
request message
service request
identifier
service
Prior art date
Application number
PCT/CN2012/070704
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 CN201280000306.6A priority Critical patent/CN103548377B/zh
Priority to PCT/CN2012/070704 priority patent/WO2013107057A1/zh
Publication of WO2013107057A1 publication Critical patent/WO2013107057A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00Encapsulation of packets

Definitions

  • the present invention belongs to the field of communications technologies, and in particular, to a method, an apparatus, and a service gateway for executing a service request SR process.
  • 3GPP developed a long-term evolution plan for mobile communication networks at the end of 2004 (Long Term Evolution, LTE), under the guidance of this evolution plan, defines a new mobile communication network architecture.
  • the architecture is flatter than 2G and 3G networks, and only the packet domain is reserved (Packet Switching, PS), so it can be called Evolved 3GPP Packet Switched Domain (Evolved 3GPP Packet Switched) Domain), also known as the Evolved Packet System (EPS).
  • PS Packet Switching
  • the network element types can be roughly divided into control plane network elements and user plane network elements.
  • the control plane network element includes a mobility management network element (Mobility Management) Entity, MME), Policy and Charging Rule Function, PCRF), etc.
  • MME mobility management network element
  • PCRF Policy and Charging Rule Function
  • the user plane network element includes a Serving Gateway (SGW) and a packet data gateway (PDN). Gateway, PGW, etc., the existing evolved packet network architecture is shown in Figure 1.
  • the mobility management network element MME is responsible for the non-access layer (Non-Access).
  • Stratum, NAS Stratum, NAS signaling processing, including NAS signaling encryption and roaming, tracking functions, assigning temporary identity and security functions to user equipment;
  • the service gateway SGW is responsible for the local mobility anchor;
  • the packet data gateway PGW is responsible for executing the policy and Billing and user plane anchors in the non-3GPP handover process.
  • the radio base station (E-UTRAN)
  • the NodeB, eNodeB) establishes an S1-MME interface with the mobility management network element, and establishes an S1-U interface with the serving gateway, wherein the E-UTRAN in FIG. 1 represents the wireless base station.
  • the S1-MME interface is mainly responsible for transmitting control plane signaling
  • the user plane S1-U interface is mainly responsible for transmitting user data.
  • the location of the user-side packet data gateway is continuously moved downward, that is, closer to the user terminal and the wireless base station.
  • the deployment location of the control plane mobility management network element is getting higher and higher.
  • the centralized deployment of the mobility management network element is more conducive to network virtualization and reduce energy consumption (such as reducing the number of computer rooms, reducing air conditioning usage, etc.). Therefore, when the mobility management network element and the service gateway are far apart, and the message signaling is rapidly increasing, frequent signaling interaction between the two will inevitably lead to waste of transmission resources.
  • the user equipment After the user equipment completes the two-way authentication authentication between the user equipment and the mobility management network element through the registration process, the user equipment negotiates a security vector with the mobility management network element. During subsequent message interactions, certain messages require security vector encryption and integrity protection.
  • the user equipment After the user equipment registers with the network, it changes from the connected state to the idle state if there is no service to do. The user equipment in the idle state will select a cell to camp and listen to the cell broadcast information, but the mobility management network element only knows the list of the tracking area where the idle user equipment is located, and cannot be accurate to a specific cell.
  • the user equipment When the idle state user equipment needs to perform the service or the idle state user equipment receives the network paging, the user equipment initiates a service request procedure, that is, the user equipment sends a service request message to the wireless side base station, and then the wireless base station sends the foregoing message to the user equipment.
  • the registered mobility management network element the mobility management network element notifies the service gateway to restore the user plane tunnel between the serving gateway and the wireless base station, and the user equipment sends the uplink data to the serving gateway through the user plane tunnel.
  • the embodiment of the present invention provides a method, an apparatus, and a service gateway for performing a service request SR process, which are intended to solve the problem that the mobility management network element and the service gateway are far apart in the mobile network architecture provided by the prior art. Frequent signaling interactions can cause waste of transmission resources.
  • a method for performing a service request SR process comprising:
  • an apparatus for performing a service request SR process comprising:
  • a message receiving unit configured to receive an initial user equipment message sent by the wireless base station, where the initial user equipment message encapsulates a service request message sent by the user equipment to the wireless base station;
  • An execution unit is configured to detect whether a current state of the user equipment meets a preset triggering policy, and if yes, execute a simplified SR process to respond to the service request message.
  • a service gateway including an execution device of a service request SR process as described above.
  • a mobile network architecture including the service gateway as described above.
  • the serving gateway after receiving the initial user equipment message sent by the radio base station, the serving gateway detects whether the current state of the user equipment meets a preset triggering policy, and if yes, performs a simplified SR procedure to respond to the service request message.
  • the implementation of the simplified SR process is implemented, and the waste of transmission resources caused by frequent interaction signaling between the mobility management network element and the serving gateway is avoided.
  • 1 is a schematic diagram of an evolved packet network architecture
  • FIG. 2 is a schematic diagram of an S1-Relay mobile network architecture
  • FIG. 3 is a schematic diagram showing an implementation flow of a method for simplifying an SR process
  • FIG. 4 is a schematic diagram showing an implementation flow of a method for executing a standard SR process
  • FIG. 5 is a flowchart of an implementation of an SR process according to Embodiment 1 of the present invention.
  • FIG. 6 is a flowchart of an implementation of a connection release process according to Embodiment 1 of the present invention.
  • FIG. 7 is a flowchart of implementing a reachability notification process of a user equipment according to Embodiment 1 of the present invention.
  • FIG. 9 is a structural block diagram of an apparatus for executing an SR process according to Embodiment 3 of the present invention.
  • the serving gateway after receiving the initial user equipment message sent by the radio base station, the serving gateway detects whether the current state of the user equipment meets a preset triggering policy, and if yes, performs a simplified SR procedure to respond to the service request message.
  • the implementation of the simplified SR process is implemented, and the waste of transmission resources caused by frequent interaction signaling between the mobility management network element and the serving gateway is avoided.
  • FIG. 2 is a schematic diagram of an S1-Relay mobile network architecture provided by an embodiment of the present invention, where an S1-MME interface is no longer directly transmitted by a wireless base station to a mobility management network element, but is forwarded through a serving gateway (SGW), that is, a serving gateway.
  • SGW serving gateway
  • It is a mandatory node for S1-MME signaling transmission and bears the processing function of part of S1-MME signaling.
  • the service gateway SGW processes the SR process locally, which is called a simplified SR process. See Figure 3 for a simplified SR process.
  • the serving gateway SGW sends the SR message to the mobility management network element MME for processing.
  • the processing scheme is the same as the existing standard process, and is called a standard SR process.
  • a standard SR process For the specific standard SR process diagram, refer to FIG. 4 .
  • FIG. 5 is a flowchart showing an implementation process of an execution method of an SR process according to an embodiment of the present invention, which is described in detail as follows:
  • step S501 an initial user equipment message sent by the radio base station is received, and the initialization user equipment message encapsulates a service request message sent by the user equipment to the radio base station.
  • the serving gateway receives an initial user equipment message sent by the wireless base station.
  • the embodiment of the present invention does not limit how the serving gateway intercepts the initial user equipment message sent by the wireless base station to the mobility management network element.
  • the temporary identification information allocated by the mobility management network element to the user includes the service gateway identifier, and the wireless base station is based on The service gateway identifier in the user temporary identifier selects the service gateway and sends the above message to the service gateway first.
  • step S502 it is detected whether the current state of the user equipment satisfies a trigger policy set in advance, and if yes, the simplified SR process is executed to respond to the service request message, and if not, the standard SR process is executed to respond to the service request message.
  • the serving gateway After receiving the initial user equipment message sent by the radio base station, the serving gateway detects whether the current state of the user equipment of the current state of the user equipment meets a preset triggering policy.
  • the current state of the user equipment may be obtained from a connection release process.
  • the simplified SR process is executed to respond to the service request message, otherwise the standard SR process is executed to respond to the service request message.
  • the triggering policy for performing the standard SR process is as follows: the security vector index identifier stored by the serving gateway is the same as the security vector index identifier sent by the user equipment through the service request message; the user equipment is not connected from the closed subscription user group cell. Entering, or the service gateway has the closed subscription user group subscription data of the user equipment; the user equipment does not need to re-authenticate authentication; the service gateway does not have a legal interception requirement identifier for the user equipment; the service gateway is not set There is a reachability reporting identifier for the user equipment; the paging response timer for the user equipment is not started in the serving gateway and the timer does not time out. As long as the serving gateway detects that the current state of the user equipment meets one of the trigger policies, the simplified SR process is executed in response to the service request message sent by the user equipment.
  • the step of detecting whether the current state of the user equipment meets the preset triggering policy specifically includes: detecting whether the security vector index identifier stored in the serving gateway is the same as the security vector index identifier sent by the wireless base station by initializing the user equipment message; or Detecting whether the user equipment is accessed from the closed subscriber group cell, and whether the service gateway has the closed subscription subscriber group subscription data of the user equipment; or detecting whether the user equipment needs to be authenticated again; or, detecting the service Whether the legal listening requirement identifier is set for the user equipment in the gateway; or detecting whether the reachability reporting identifier is set for the user equipment in the service gateway; or detecting whether the paging response timing for the user equipment is started in the serving gateway And this timer has not timed out.
  • the serving gateway compares whether the KSI parameter sent by the user equipment is the same as the KSI parameter stored by the serving gateway. When the two are the same, the simplified SR process is executed.
  • the step of detecting whether the security vector index identifier stored in the service gateway is the same as the security vector index identifier sent by the radio base station by initializing the user equipment message is specifically:
  • the service gateway first reads the user equipment context data (including the security vector index identifier KSI, the key and the security algorithm, and so on), extracts the security vector index identifier KSI, and parses the initial user equipment sent by the wireless base station.
  • the message extracts the KSI included in the service request message sent by the user equipment, and compares whether the KSI sent by the user equipment is the same as the KSI stored on the service gateway. If they are the same, the simplified SR process is executed; if different, the service is performed.
  • the gateway must forward the initialized user equipment message encapsulating the service request message sent by the user equipment to the mobility management network element, that is, perform a standard SR procedure.
  • connection release process The process of storing the user device context data by the service gateway can be implemented in the connection release process.
  • the specific connection release process is as shown in FIG. 6, and includes:
  • Step 11 In the connection release process, the serving gateway receives an access bearer release request message sent by the mobility management network element, where the access bearer release request message includes a security vector index identifier.
  • the mobility management network element initiates a connection release process and sends an access bearer release request message (Release Access Bearer) Request, RABR) to the service gateway, which carries the NAS
  • RABR access bearer release request message
  • the above message may also include user temporary identification information (GUTI), and bear the quality of service. (Quality of Service, QoS), User Equipment Aggregate Maximum Bit Rate, UE AMBR), Tracking Area List (TA List) and other parameters, the above parameters can be collectively referred to as user equipment context data.
  • Step 12 The serving gateway stores the security vector index identifier.
  • the serving gateway receives the access bearer release request message sent by the mobility management network element, extracts user equipment context data, and stores the data.
  • the stored user equipment context data includes a security vector index identifier KSI.
  • the parameters required in the SR process triggering policy such as the security vector index identifier KSI, are synchronized to the serving gateway by the mobility management network element, and the serving gateway stores the user equipment context data, and initiates a service request message at the user equipment.
  • the simplified SR process or the standard SR process is automatically executed based on a trigger policy that is preset in the service gateway to execute a standard SR process.
  • Step 13 The serving gateway replies to the access bearer release response message to the mobility management network element.
  • the serving gateway detects that the user equipment does not access the closed subscription user group subscription data from the closed subscription user group or the service gateway, the simplified SR process is executed to respond to the service request message.
  • the service gateway sends a service request message to the mobility management network element, that is, performs a standard SR process.
  • the step of detecting whether the user equipment is accessed from the closed subscriber group cell, and whether the service gateway has the closed subscription subscriber group subscription data of the user equipment is specifically:
  • the serving gateway obtains the cell identifier accessed by the user equipment from the received initial user equipment message, where the initial user equipment message is reported by the radio base station to the serving gateway, and if the user equipment accesses from the CSG cell, the user equipment message is initialized. It must also contain the CSG cell identity. Therefore, the serving gateway can determine whether the user accesses through the CSG cell by initializing whether the user equipment message contains the CSG cell identifier. If the user equipment accesses from the CSG cell, the serving gateway needs to forward the service request message to the mobility management network element, that is, perform a standard SR procedure.
  • the mobility management network element needs to re-authenticate the user and generate a new set of security vectors. Therefore, when the user equipment authenticates the authentication again, the serving gateway needs to send the service request message to the mobility management network element, that is, the standard SR process is executed, and when it is detected that the user equipment does not need to perform the authentication again, the simplified SR process is performed.
  • the specific method for detecting whether the user equipment needs to be authenticated again is not limited, and only one example is determined according to the number of message interactions to determine whether authentication authentication is required again.
  • the detailed steps include:
  • Step 31 Count the number of signaling interactions between the user equipment and the mobility management network element.
  • Step 32 After the number of signaling interactions is greater than the maximum number of interactions preset by the operator, the user equipment is authenticated again.
  • the operator sets the maximum number of signaling interactions on the serving gateway.
  • the service gateway records the number of message interactions between the user equipment and the mobility management network element. When the total number of messages reaches the maximum number of times configured by the operator, it indicates that The user equipment performs re-authentication authentication, and the service gateway sends a service request message to the mobility management network element, that is, performs a standard SR process.
  • the service gateway sends the received service request message to the service gateway.
  • the mobility management network element performs the standard SR process. If the lawful interception function for the user equipment is not enabled on the mobility management network element, the simplified SR process is executed.
  • the service gateway must perform the following steps before detecting whether the legal device needs to set the lawful interception requirement identifier for the user equipment:
  • Step 41 Monitor whether the mobility management network element initiates a lawful interception operation for the user equipment.
  • the service gateway obtains the lawful interception function for the user equipment by the mobility management network element.
  • the present invention is not limited.
  • the mobility management network element starts the lawful interception function
  • the mobility management network element sends a lawful interception start message to the service.
  • the above message includes identification information of the monitored user equipment, such as a permanent identifier of the user (International Mobile Subscriber Identification Number , IMSI).
  • IMSI International Mobile Subscriber Identification Number
  • the service gateway sets a lawful interception requirement identifier for the user equipment. Before the identifier is cleared, the service gateway sends the service request message sent by the user equipment to the mobility management network element, that is, the standard SR process is executed. .
  • Step 42 If the mobility management network element initiates a lawful interception operation for the user equipment, set a lawful interception requirement identifier for the user equipment in the service gateway.
  • the service gateway After the service gateway receives the lawful interception start message sent by the mobility management network element, it is known that the mobility management network element has initiated a lawful interception operation for the user equipment included in the message, and the user equipment is in the service gateway.
  • the legal interception requirement identifier is set. Before the identifier is cleared, the service gateway sends the service request message sent by the user equipment to the mobility management network element, that is, performs a standard SR process.
  • the reachability report identifier must be set for the user equipment in the service gateway.
  • the standard SR process must be performed. If the reachability report identifier is not required for the user equipment. , the implementation of the simplified SR process.
  • the user equipment reachability notification process Before detecting the step of setting the reachability report identifier for the user equipment in the service gateway, the user equipment reachability notification process must also be performed.
  • the process is as shown in FIG. 7, and includes:
  • Step 51 The home subscriber server HSS sends a user equipment reachability notification request (Reachability Notification Request, RNQ) to the mobility management network element.
  • RNQ a user equipment reachability notification request
  • the home subscriber server HSS sends a user equipment reachability notification request (Reachability Notification) Request, RNQ) A mobility management network element attached to the user equipment.
  • RNQ a mobility management network element attached to the user equipment.
  • the mobility management network element needs to notify the home subscriber server.
  • Step 52 The mobility management network element forwards the user equipment reachability notification request to the serving gateway.
  • the mobility management network element For the user equipment in the idle state, the mobility management network element sends a user reachability notification request to the service gateway attached to the user equipment, where the notification request includes user identification information, such as a permanent identifier (IMSI) or temporary identifier information of the user (GUTI) and so on.
  • the service gateway After receiving the foregoing notification request, the service gateway sets a reachability report identifier for the user equipment.
  • the home subscriber server may notify the mobility management network element to stop the user reachability reporting operation. If the mobility management network element does not need to report the user equipment reachability information to the home subscriber server, the mobility management network element clears the reachability report identifier previously set on the service gateway.
  • Step 53 The serving gateway monitors whether the user equipment reachability notification request forwarded by the mobility management network element is received.
  • the mobility management network element forwards the notification request to the service gateway to notify the service gateway to report the user equipment reachability message when the user equipment connects to the network.
  • Step 54 If the user equipment reachability notification request forwarded by the mobility management network element is received, the reachability report identifier is set for the user equipment in the service gateway.
  • the service gateway monitors whether the user equipment reachability notification request forwarded by the mobility management network element is received. If the user equipment reachability notification request forwarded by the mobility management network element is received, the requirement for the HSS is set for the user equipment.
  • the service report message is sent to the mobility management network element, that is, the standard SR process is executed.
  • FIG. 8 is a flowchart of an implementation process of a service request SR process according to Embodiment 2 of the present invention.
  • the method can be applied to a S1-Relay move that can perform a standard SR process or a simplified SR process including a service gateway.
  • the details are as follows:
  • the user equipment sends a service request message to the wireless base station.
  • the service request message sent by the user equipment is encapsulated in the radio resource control (Radio Resource).
  • the Control, RRC) message is sent to the radio base station.
  • the RRC message includes the temporary identification information assigned by the mobility management network element to the user and the attached mobility management network element identifier.
  • the radio base station encapsulates the service request message in an initial user equipment message.
  • the radio base station encapsulates the service request message sent by the user equipment in the initialization user equipment message (Initial UE The Message, IUM) is sent to the mobility management network element, and the initial user equipment message further includes the cell identity information of the user equipment connection. If the user accesses from the CSG cell, the foregoing message further includes a CSG cell identifier and an access mode of the CSG cell, that is, a closed CSG cell mode or a hybrid CSG cell mode.
  • the service gateway receives the initial user equipment message sent by the wireless base station, where the initial user equipment message encapsulates a service request message sent by the user equipment to the wireless base station.
  • the present invention does not limit how the serving gateway intercepts the initial user equipment message sent by the wireless base station to the mobility management network element.
  • the temporary identification information allocated by the mobility management network element to the user equipment includes the service gateway identifier, and the wireless base station may be based on The serving gateway identifier in the user temporary identifier selects the serving gateway, and first sends the above initial user equipment message to the serving gateway.
  • the service gateway detects whether the current state of the user equipment meets the preset trigger policy, and if yes, performs a simplified SR process, otherwise, the simplified SR process is executed to respond to the service request message, and the intercepted initialized user equipment message is forwarded to mobility. Manage network elements.
  • the serving gateway forwards the intercepted initial user equipment message to the mobility management network element.
  • FIG. 9 is a block diagram showing a specific structure of an apparatus for executing a service request SR process according to an embodiment of the present invention.
  • the device is a software unit, a hardware unit or a combination of software and hardware built in the service gateway, and the service gateway can be applied in the S1-Relay mobile network architecture as shown in FIG. 2.
  • the apparatus includes a message receiving unit 91 and an executing unit 92.
  • the message receiving unit 91 is configured to receive an initial user equipment message sent by the radio base station, where the initial user equipment message encapsulates a service request message sent by the user equipment to the radio base station;
  • the executing unit 92 is configured to detect whether the current state of the user equipment meets a preset triggering policy, and if yes, execute a simplified SR process to respond to the service request message, and if not, execute a standard SR process to respond to the service request message.
  • the executing unit 92 includes: an identifier detecting module or a cell access detecting module or a re-authentication detecting module or a monitoring demand detecting module or a reachability reporting detecting module or a timer detecting module.
  • the identifier detecting module is configured to detect whether the security vector index identifier stored in the serving gateway is the same as the security vector index identifier sent by the wireless base station by initializing the user equipment message, and if the same, execute the simplified SR process to respond to the service request.
  • the cell access detection module is configured to detect whether the user equipment is accessed from the closed subscriber group cell, and whether the service gateway has the closed subscription subscriber group subscription data of the user equipment, if the user equipment does not from the closed subscription subscriber group If the cell access or the service gateway has the closed subscription user group subscription data of the user equipment, the simplified SR process is executed to respond to the service request message;
  • the re-authentication detection module is configured to detect whether the user equipment needs to be authenticated again, and if the authentication authentication is not required, executing the simplified SR process to respond to the service request message;
  • the monitoring requirement detecting module is configured to detect whether a legal listening requirement identifier is set for the user equipment in the service gateway, and if the legal listening requirement identifier is not set for the user equipment, executing the simplified SR process to respond to the service request message;
  • the reachability report detection module is configured to detect whether a reachability report identifier is set for the user equipment in the service gateway. If the reachability report identifier is not set for the user equipment, the simplified SR process is executed to respond to the service request message. ;
  • the timer detecting module is configured to detect whether a paging response timer for the user equipment is started in the serving gateway, and the timer does not time out. If the paging response timer for the user equipment is not started in the serving gateway, or the timer is exceeded, Then, the simplified SR process is executed in response to the service request message.
  • the identifier detection module includes: a context data acquisition submodule, a first KSI extraction submodule, a second KSI extraction submodule, and a KSI comparison submodule.
  • the context data acquisition sub-module is configured to obtain user equipment context data stored by the service gateway itself;
  • a first KSI extraction submodule configured to extract a security vector index identifier KSI from the user equipment context data
  • a second KSI extraction submodule configured to parse an initial user equipment message sent by the radio base station, and extract, from the initial user equipment message, a KSI included in a service request message sent by the user equipment;
  • the KSI comparison submodule is configured to compare whether the KSI sent by the user equipment is the same as the KSI stored on the serving gateway.
  • the apparatus further includes: a bearer release request receiving unit and a security vector index storage unit.
  • the bearer release request receiving unit is configured to receive, in the connection release process, an access bearer release request message sent by the mobility management network element, where the access bearer release request message includes a security vector index identifier;
  • a security vector index storage unit is used to store the security vector index identifier.
  • the re-authentication detection module includes: an interaction count statistics sub-module and a re-authentication judgment sub-module.
  • the interaction number statistics sub-module is used to count the number of signaling interactions between the user equipment and the mobility management network element.
  • the re-authentication judging sub-module is configured to perform re-authentication authentication on the user equipment after the number of signaling interactions counted by the statistics sub-module is greater than the maximum number of interactions preset by the operator.
  • the device further includes: a legal monitoring monitoring unit and a legal monitoring setting unit.
  • the lawful interception monitoring unit is configured to monitor whether the mobility management network element initiates a lawful interception operation for the user equipment;
  • the lawful interception setting unit is configured to set a legal interception requirement identifier for the user equipment in the service gateway when the legal monitoring monitoring unit detects that the mobility management network element initiates a lawful interception operation for the user equipment.
  • the device further includes: a reachability report monitoring unit and a reachability report setting unit, in order to enable the reachability report detection module to obtain the reachability report identifier stored in the service gateway.
  • the reachability reporting monitoring unit is configured to monitor whether the user equipment reachability notification request forwarded by the mobility management network element is received
  • the reachability report setting unit is configured to: when the reachability report monitoring unit detects that the service gateway has received the user equipment reachability notification request forwarded by the mobility management network element, set the user equipment in the service gateway. Upgrading the identifier.
  • the serving gateway after receiving the initial user equipment message sent by the radio base station, the serving gateway detects whether the current state of the user equipment meets a preset triggering policy, and if yes, performs a simplified SR procedure to respond to the service request message.
  • the implementation of the simplified SR process is implemented, and the waste of transmission resources caused by frequent interaction signaling between the mobility management network element and the serving gateway is avoided.

Landscapes

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

Abstract

本发明适用于通信技术领域,提供了一种服务请求SR流程的执行方法、装置及服务网关,所述方法包括:接收无线基站发送的初始化用户设备消息,所述初始化用户设备消息中封装有用户设备发送至无线基站的服务请求消息;检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息。本发明可以在S1-Relay移动网络架构下,实现简化SR流程的执行,减少传输资源的浪费。

Description

一种服务请求SR流程的执行方法、装置及服务网关 技术领域
本发明属于通信技术领域,尤其涉及一种服务请求SR流程的执行方法、装置及服务网关。
背景技术
为了应对无线宽带技术的挑战,保持3GPP网络的领先优势,3GPP在2004年底制定了移动通信网络的长期演进计划(Long Term Evolution,LTE),在此演进计划的指导下,定义了新的移动通信网络架构。该架构比2G、3G网络更加扁平化,并且只保留了分组域(Packet Switching,PS),因此可以称为演进的3GPP分组交换域(Evolved 3GPP Packet Switched Domain),也可称之为演进的分组系统(Evolved Packet System,EPS)。
在新的移动网络架构中,网元类型大致可分为控制面网元与用户面网元。其中,控制面网元包括移动性管理网元(Mobility Management Entity,MME)、策略控制实体(Policy and Charging Rule Function,PCRF)等。而用户面网元包括服务网关(Serving Gateway,SGW)、分组数据网关(PDN Gateway,PGW)等,现有演进分组网络架构如图1所示。移动性管理网元MME负责非接入层(Non-Access Stratum,NAS)信令的处理,包括NAS信令加密以及漫游、跟踪功能,为用户设备分配临时身份标识以及安全功能等;服务网关SGW负责本地的移动锚点;分组数据网关PGW负责执行策略和计费以及与非3GPP切换过程中的用户面锚点。
上述网络架构中,无线基站(E-UTRAN NodeB,eNodeB)与移动性管理网元建立S1-MME接口,与服务网关建立S1-U接口,其中,图1中的E-UTRAN表示无线基站。S1-MME接口主要负责传递控制面信令,而用户面S1-U接口主要负责传递用户数据。近年来,随着移动智能终端的迅猛发展,用户数据量与消息信令数量急剧增加。为了更好的为用户提供服务,用户面分组数据网关部署位置不断下移,即离用户终端及无线基站位置越来越近。而与此相反,控制面移动性管理网元的部署位置却越来越高。集中部署后的移动性管理网元更有利于实现网络虚拟化及减少能源消耗(如减少机房数量、降低空调使用等等)。由此,在移动性管理网元与服务网关距离较远,而消息信令急剧增长的今天,两者之间频繁的信令交互势必导致传输资源的浪费。
目前, SR流程执行的过程是:
用户设备通过注册流程完成用户设备与移动性管理网元之间的双向鉴权认证后,用户设备与移动性管理网元协商安全向量。后续消息交互过程中,某些消息需要通过安全向量加密和完整性保护。用户设备注册到网络后,如果没有业务要做则从连接态变为空闲态。处在空闲态的用户设备将选择一个小区驻留,监听该小区广播信息,但移动性管理网元只知道空闲态用户设备所在跟踪区列表,无法精确到某个具体小区。当空闲态用户设备需要进行业务或空闲态用户设备接收到网络寻呼时,用户设备发起服务请求流程,即用户设备发送服务请求消息到无线侧基站,再由无线基站将上述消息发送给用户设备注册的移动性管理网元,移动性管理网元通知服务网关恢复服务网关与无线基站之间的用户面隧道,用户设备将上行数据通过用户面隧道发送给服务网关。
从上述SR流程执行的过程,可以看出,采用如上所述的SR流程执行的技术方案,则无法实现简化的SR流程操作,移动性管理网元与服务网关之间仍然需要频繁的信令交互,会导致传输资源的浪费。
技术问题
本发明实施例提供了一种服务请求SR流程的执行方法、装置及服务网关,旨在解决现有技术提供的移动网络架构中,移动性管理网元与服务网关距离较远,两者之间频繁的信令交互会导致传输资源的浪费的问题。
技术解决方案
一方面,提供一种服务请求SR流程的执行方法,所述方法包括:
接收无线基站发送的初始化用户设备消息,所述初始化用户设备消息中封装有用户设备发送至无线基站的服务请求消息;
检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息。
另一方面,提供一种服务请求SR流程的执行装置,所述装置包括:
消息接收单元,用于接收无线基站发送的初始化用户设备消息,所述初始化用户设备消息中封装有用户设备发送至无线基站的服务请求消息;
执行单元,用于检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息。
再一方面,提供一种服务网关,所述服务网关包括如上所述的服务请求SR流程的执行装置。
又一方面,提供一种移动网络架构,所述移动网络架构中包括如上所述的服务网关。
有益效果
在本发明实施例中,服务网关接收到无线基站发送的初始化用户设备消息后,检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息。使得在S1-Relay移动网络架构下,实现了简化SR流程的执行,避免了由于移动性管理网元和服务网关之间频繁交互信令导致的传输资源的浪费。
附图说明
图1是演进分组网络架构示意图;
图2是S1-Relay移动网络架构示意图;
图3是简化SR流程的执行方法的实现流程示意图;
图4是标准SR流程的执行方法的实现流程示意图;
图5是本发明实施例一提供的SR流程的执行方法的实现流程图;
图6是本发明实施例一提供的连接释放流程的实现流程图;
图7是本发明实施例一提供的用户设备可达性通知流程的实现流程图;
图8是本发明实施例二提供的SR流程的执行方法的实现流程;
图9是本发明实施例三提供的SR流程的执行装置的结构框图。
本发明的实施方式
为了使本发明的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本发明进行进一步详细说明。应当理解,此处所描述的具体实施例仅仅用以解释本发明,并不用于限定本发明。
在本发明实施例中,服务网关接收到无线基站发送的初始化用户设备消息后,检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息。使得在S1-Relay移动网络架构下,实现了简化SR流程的执行,避免了由于移动性管理网元和服务网关之间频繁交互信令导致的传输资源的浪费。
图2示出了本发明实施例提供的S1-Relay移动网络架构,其中,S1-MME接口不再由无线基站直接到移动性管理网元,而是通过服务网关(SGW)转发,即服务网关作为S1-MME信令传输的必经节点并承担部分S1-MME信令的处理功能。具体来讲,当用户设备有业务要做,并发起服务请求流程(Service Request Procedure,SR流程)时,服务网关SGW可视情况在本地处理该SR流程,称为简化SR流程,具体的简化SR流程示意图请参见图3。或在其他情况下,服务网关SGW将SR消息发送给移动性管理网元MME进行处理,处理方案同现有标准流程,称为标准SR流程,具体的标准SR流程示意图请参见图4。
实施例一
图5示出了本发明实施例提供的SR流程的执行方法的实现流程,详述如下:
在步骤S501中,接收无线基站发送的初始化用户设备消息,所述初始化用户设备消息中封装有用户设备发送至无线基站的服务请求消息。
服务网关接收无线基站发送的初始化用户设备消息。本发明实施例不对服务网关如何截获无线基站发往移动性管理网元的初始化用户设备消息的方法做限制,比如移动性管理网元分配给用户的临时标识信息中含有服务网关标识,无线基站基于用户临时标识中的服务网关标识选择服务网关,并将上述消息首先发送给该服务网关。
在步骤S502中,检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息,如果否,则执行标准SR流程响应所述服务请求消息。
服务网关接收到无线基站发送的初始化用户设备消息后,检测用户设备的当前状态用户设备的当前状态是否满足预先设置的触发策略。
其中,可以从连接释放流程中获取所述用户设备的当前状态。
当用户设备的当前状态满足预先设置的触发策略时,则执行简化SR流程响应所述服务请求消息,否则执行标准SR流程响应所述服务请求消息。
其中,预先设置的执行标准SR流程的触发策略包括:服务网关存储的安全向量索引标识符与用户设备通过服务请求消息发送的安全向量索引标识符相同;用户设备未从封闭签约用户群组小区接入,或者服务网关中有所述用户设备的封闭签约用户群组签约数据;用户设备不需要再次鉴权认证;服务网关中未设置有针对用户设备的合法监听需求标识符;服务网关中未设置有针对用户设备的可达性上报标识符;服务网关中未启动针对用户设备的寻呼响应定时器且此定时器未超时。只要服务网关检测到用户设备的当前状态满足上述触发策略中的其中一条,则执行简化SR流程响应用户设备发送的所述服务请求消息。
其中,检测用户设备的当前状态是否满足预先设置的触发策略的步骤具体包括:检测服务网关中存储的安全向量索引标识符与无线基站通过初始化用户设备消息发送的安全向量索引标识符是否相同;或,检测用户设备是否从封闭签约用户群组小区接入,并且服务网关中是否具有所述用户设备的封闭签约用户群组签约数据;或,检测用户设备是否需要再次鉴权认证;或,检测服务网关中是否为用户设备设置了合法监听需求标识符;或,检测服务网关中是否为用户设备设置了可达性上报标识符;或,检测服务网关中是否启动了针对用户设备的寻呼响应定时器且此定时器未超时。
下面分别对各个检测步骤进行介绍:
1、服务网关比较用户设备发送的KSI参数与服务网关存储的KSI参数是否相同,当两者相同时,执行简化的SR流程。
检测服务网关中存储的安全向量索引标识符与无线基站通过初始化用户设备消息发送的安全向量索引标识符是否相同的步骤具体为:
服务网关首先读取自身所存储的用户设备上下文数据(包括安全向量索引标识符KSI、密钥与安全算法等参量),从中提取出安全向量索引标识符KSI,同时解析无线基站发送的初始化用户设备消息,从中提取出用户设备发送的服务请求消息中所包含的KSI,再比较用户设备发送的KSI与服务网关上存储的KSI是否相同,如果相同,则执行简化的SR流程;如果不同,则服务网关必须将封装有用户设备发送的服务请求消息的初始化用户设备消息转发给移动性管理网元,即执行标准的SR流程。
其中,服务网关存储用户设备上下文数据的过程可在连接释放流程中实现,具体的连接释放流程如图6所示,包括:
步骤11、在连接释放流程中,服务网关接收移动性管理网元发送的接入承载释放请求消息,所述接入承载释放请求消息中包括安全向量索引标识符。
移动性管理网元发起连接释放流程,发送接入承载释放请求消息(Release Access Bearer Request,RABR)至服务网关,其中携带NAS 信令交互次数、安全向量索引标识符KSI、用户设备与移动性管理网元协商的加密与完整性保护算法及安全密钥等参量。此外,上述消息中还可能包含用户临时标识信息(GUTI)、承载服务质量 (Quality of Service,QoS),用户设备最大聚合带宽(User Equipment Aggregate Maximum Bit Rate,UE AMBR),跟踪区列表(Tracking Area List ,TA List)等参量,上述参量可以统称为用户设备上下文数据。
步骤12、服务网关存储所述安全向量索引标识符。
服务网关接收到移动性管理网元发送的接入承载释放请求消息,从中提取出用户设备上下文数据,并进行存储。其中,存储的用户设备上下文数据中包括安全向量索引标识符KSI。
本实施例,通过移动性管理网元将SR流程触发策略中所需的参数,比如安全向量索引标识符KSI同步到服务网关,服务网关存储用户设备上下文数据后,并在用户设备发起服务请求消息时基于服务网关中预先设置的执行标准SR流程的触发策略自动执行简化SR流程或标准SR流程。
步骤13、服务网关回复接入承载释放响应消息给移动性管理网元。
2、当服务网关检测到用户设备不从封闭签约用户群组小区接入或者服务网关中具有所述用户设备的封闭签约用户群组签约数据时,执行简化SR流程响应所述服务请求消息,当检测到用户设备从CSG小区接入,且服务网关上没有用户CSG签约数据时,则服务网关将服务请求消息发送给移动性管理网元,即执行标准的SR流程。
检测用户设备是否从封闭签约用户群组小区接入,并且服务网关中是否具有所述用户设备的封闭签约用户群组签约数据的步骤具体为:
服务网关从接收到的初始化用户设备消息中获得用户设备接入的小区标识,所述初始化用户设备消息是无线基站上报给服务网关的,如果用户设备从CSG小区接入,则初始化用户设备消息中还必须包含CSG小区标识。因此,服务网关可以通过初始化用户设备消息中是否含有CSG小区标识判别用户是否通过CSG小区接入。如果用户设备从CSG小区接入,则服务网关需要将服务请求消息转发给移动性管理网元,即执行标准的SR流程。
3、为了保证用户设备与移动性管理网元交互的信息安全,当一组安全向量使用一段时间后,移动性管理网元需要对用户重新进行鉴权认证并生成新的一组安全向量。因此当用户设备再次鉴权认证时,服务网关需要将服务请求消息发送给移动性管理网元,即执行标准SR流程,当检测到用户设备不需要再次鉴权认证时,执行简化SR流程。
具体的检测用户设备是否需要再次鉴权认证的方案本发明不做限制,只举一个根据消息交互次数决定是否需要再次鉴权认证的例子来进行说明,详细的步骤包括:
步骤31、统计用户设备与移动性管理网元之间的信令交互次数。步骤32、当所述信令交互次数大于运营商预先设置的最大交互次数上限后,则对所述用户设备进行再次鉴权认证。
运营商在服务网关上设置最大信令交互次数,服务网关记录用户设备与移动性管理网元之间的消息交互次数,当此消息总量达到运营商配置的最大次数上限时,则表示需要对所述用户设备进行再次鉴权认证,服务网关将服务请求消息发送给移动性管理网元,即执行标准SR流程。
4、如果移动性管理网元上启动了针对用户设备的合法监听功能,即移动性管理网元需要监听该用户设备发送的所有消息信令时,则服务网关将接收到的服务请求消息发送给移动性管理网元,即执行标准的SR流程,如果移动性管理网元上未启动针对用户设备的合法监听功能,则执行简化的SR流程。
其中,在检测服务网关中是否为用户设备设置了合法监听需求标识符的步骤之前,服务网关必须执行以下步骤:
步骤41、监测移动性管理网元是否启动了针对用户设备的合法监听操作。
服务网关获取移动性管理网元启动针对用户设备的合法监听功能的方案本发明不做限制,例如,当移动性管理网元启动合法监听功能后,移动性管理网元发送合法监听启动消息给服务网关,上述消息中包含被监听用户设备的标识信息,如用户永久标识(International Mobile Subscriber Identification Number ,IMSI)。服务网关收到上述消息后,针对该用户设备设置合法监听需求标识符,在此标识被清除之前,服务网关将该用户设备发送的服务请求消息发送给移动性管理网元,即执行标准SR流程。
步骤42、如果移动性管理网元启动了针对用户设备的合法监听操作,则在服务网关中为用户设备设置合法监听需求标识符。
当服务网关接收到移动性管理网元发送的合法监听启动消息后,得知移动性管理网元已经针对该消息中所包括的用户设备启动了合法监听操作,则在服务网关中为该用户设备设置合法监听需求标识符,在此标识被清除之前,服务网关将该用户设备发送的服务请求消息发送给移动性管理网元,即执行标准SR流程。
5、如果归属服务器HSS需要用户设备可达性信息,则在服务网关中必须为用户设备设置可达性上报标识符,必须执行标准SR流程,如果不需要为用户设备设置可达性上报标识符,则执行简化SR流程。
检测服务网关中是否为用户设备设置了可达性上报标识符的步骤之前,还必须执行用户设备可达性通知流程,所述流程如图7所示,包括:
步骤51、归属用户服务器HSS发送用户设备可达性通知请求(Reachability Notification Request,RNQ)给移动性管理网元。
归属用户服务器HSS发送用户设备可达性通知请求(Reachability Notification Request,RNQ)给用户设备附着的移动性管理网元,对于上述用户设备,当其连接网络时,移动性管理网元需要通知归属用户服务器。
步骤52、移动性管理网元转发所述用户设备可达性通知请求至服务网关。
对于空闲态的用户设备,移动性管理网元发送用户可达性通知请求给用户设备附着的服务网关,上述通知请求中包含用户标识信息,如用户永久标识(IMSI),或用户临时标识信息(GUTI)等。服务网关接收到上述通知请求后,为该用户设备设置可达性上报标识符。
当归属用户服务器获得用户设备处于连接态后,归属用户服务器可能通知移动性管理网元停止用户可达性上报操作。如果移动性管理网元无需上报用户设备可达性信息给归属用户服务器,则移动性管理网元将清除服务网关上之前设置的可达性上报标识符。
步骤53、服务网关监测是否接收到移动性管理网元转发的用户设备可达性通知请求。
移动性管理网元将所述通知请求转发给服务网关,以通知服务网关在用户设备连接网络时上报用户设备可达性消息。
步骤54、如果接收到移动性管理网元转发的用户设备可达性通知请求,则在服务网关中为用户设备设置可达性上报标识符。
服务网关监测是否接收到移动性管理网元转发的用户设备可达性通知请求,如果接收到移动性管理网元转发的用户设备可达性通知请求,则针对HSS的需求为上述用户设备设置可达性上报标识符,在此标识被清除之前,服务网关将用户设备发送的服务请求消息发送给移动性管理网元,即执行标准SR流程。
实施例二
图8示出了本发明实施例二提供的服务请求SR流程的执行方法的实现流程,该方法可以应用于包括服务网关的既可以执行标准SR流程,也可以执行简化SR流程的S1-Relay移动网络架构中,详述如下:
1、用户设备发送服务请求消息至无线基站。
其中,用户设备发送的服务请求消息封装在无线资源控制(Radio Resource Control,RRC)消息中发送给无线基站。
RRC消息中包含移动性管理网元分配给用户的临时标识信息及其附着的移动性管理网元标识。
2、无线基站将所述服务请求消息封装在初始化用户设备消息中。
无线基站将用户设备发送的服务请求消息封装在初始化用户设备消息(Initial UE Message,IUM)中发送给移动性管理网元,初始化用户设备消息中还包括用户设备连接的小区标识信息。如果用户从CSG小区接入,则上述消息中还包括CSG小区标识及CSG小区的接入模式,即闭合CSG小区模式或者混合CSG小区模式。
3、服务网关接收无线基站发送的初始化用户设备消息,所述初始化用户设备消息中封装有用户设备发送至无线基站的服务请求消息。
本发明不对服务网关如何截获无线基站发往移动性管理网元的初始化用户设备消息的方法做限制,比如移动性管理网元分配给用户设备的临时标识信息中含有服务网关标识,无线基站可以基于用户临时标识中的服务网关标识选择服务网关,并将上述初始化用户设备消息首先发送给该服务网关。
4、服务网关检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程,否则执行简化SR流程响应所述服务请求消息,将截获的初始化用户设备消息转发至移动性管理网元。
5、服务网关将截获的初始化用户设备消息转发至移动性管理网元。
具体可参照图5 所示方法实施例,在此不再赘述。
图9示出了本发明实施例提供的服务请求SR流程的执行装置的具体结构框图,为了便于说明,仅示出了与本发明实施例相关的部分。在本实施例中,所述装置是内置于服务网关的软件单元、硬件单元或者软硬件结合的单元,并且该服务网关可以应用在如图2所示的S1-Relay移动网络架构中。所述装置包括消息接收单元91和执行单元92。
其中,消息接收单元91用于接收无线基站发送的初始化用户设备消息,所述初始化用户设备消息中封装有用户设备发送至无线基站的服务请求消息;
执行单元92用于检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息,如果否,则执行标准SR流程响应所述服务请求消息。
进一步地,所述执行单元92包括:标识符检测模块或小区接入检测模块或再次鉴权检测模块或监听需求检测模块或可达性上报检测模块或定时器检测模块。
其中,标识符检测模块用于检测服务网关中存储的安全向量索引标识符与无线基站通过初始化用户设备消息发送的安全向量索引标识符是否相同,如果相同,则执行简化SR流程响应所述服务请求消息;
小区接入检测模块用于检测用户设备是否从封闭签约用户群组小区接入,并且服务网关中是否具有所述用户设备的封闭签约用户群组签约数据,如果用户设备不从封闭签约用户群组小区接入或者服务网关中具有所述用户设备的封闭签约用户群组签约数据,则执行简化SR流程响应所述服务请求消息;
再次鉴权检测模块用于检测用户设备是否需要再次鉴权认证,如果不需要再次鉴权认证,则执行简化SR流程响应所述服务请求消息;
监听需求检测模块用于检测服务网关中是否为用户设备设置了合法监听需求标识符,如果没有为用户设备设置了合法监听需求标识符,则执行简化SR流程响应所述服务请求消息;
可达性上报检测模块用于检测服务网关中是否为用户设备设置了可达性上报标识符,如果没有为用户设备设置了可达性上报标识符,则执行简化SR流程响应所述服务请求消息;
定时器检测模块用于检测服务网关中是否启动了针对用户设备的寻呼响应定时器且此定时器未超时,如果服务网关中未启动针对用户设备的寻呼响应定时器或者此定时器超,则执行简化SR流程响应所述服务请求消息。
进一步地,所述标识符检测模块包括:上下文数据获取子模块、第一KSI提取子模块、第二KSI提取子模块和KSI比较子模块。
其中,上下文数据获取子模块,用于获取服务网关自身所存储的用户设备上下文数据;
第一KSI提取子模块,用于从所述用户设备上下文数据中提取出安全向量索引标识符KSI;
第二KSI提取子模块,用于解析无线基站发送的初始化用户设备消息,从所述初始化用户设备消息中提取出用户设备发送的服务请求消息中所包含的KSI;
KSI比较子模块,用于比较用户设备发送的KSI与服务网关上存储的KSI是否相同。
另外,为了使标识符检测模块能够获取到服务网关中存储的安全向量索引标识符,所述装置还包括:承载释放请求接收单元和安全向量索引存储单元。
其中,承载释放请求接收单元用于在连接释放流程中,接收移动性管理网元发送的接入承载释放请求消息,所述接入承载释放请求消息中包括安全向量索引标识符;
安全向量索引存储单元用于存储所述安全向量索引标识符。
进一步地,所述再次鉴权检测模块包括:交互次数统计子模块和再次鉴权判断子模块。
其中,交互次数统计子模块用于统计用户设备与移动性管理网元之间的信令交互次数;
再次鉴权判断子模块用于当所述交互次数统计子模块统计的信令交互次数大于运营商预先设置的最大交互次数上限后,则对所述用户设备进行再次鉴权认证。
进一步地,为了使监听需求检测模块能够获取到服务网关中存储的合法监听需求标识符,所述装置还包括:合法监听监测单元和合法监听设置单元。
其中,合法监听监测单元用于监测移动性管理网元是否启动了针对用户设备的合法监听操作;
合法监听设置单元用于当所述合法监听监测单元监测到移动性管理网元启动了针对用户设备的合法监听操作时,则在服务网关中为用户设备设置合法监听需求标识符。
进一步地,为了使可达性上报检测模块能够获取到服务网关中存储的可达性上报标识符,所述装置还包括:可达性上报监测单元和可达性上报设置单元。
可达性上报监测单元用于监测是否接收到移动性管理网元转发的用户设备可达性通知请求;
可达性上报设置单元用于当所述可达性上报监测单元监测到服务网关已经接收到移动性管理网元转发的用户设备可达性通知请求时,则在服务网关中为用户设备设置可达性上报标识符。
具体可参照图5 所示方法实施例,在此不再赘述。
在本发明实施例中,服务网关接收到无线基站发送的初始化用户设备消息后,检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息。使得在S1-Relay移动网络架构下,实现了简化SR流程的执行,避免了由于移动性管理网元和服务网关之间频繁交互信令导致的传输资源的浪费。
以上所述仅为本发明的较佳实施例而已,并不用以限制本发明,凡在本发明的精神和原则之内所作的任何修改、等同替换和改进等,均应包含在本发明的保护范围之内。

Claims (20)

1、一种服务请求SR流程的执行方法,其特征在于,所述方法包括:
接收无线基站发送的初始化用户设备消息,所述初始化用户设备消息中封装有用户设备发送至无线基站的服务请求消息;
检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息。
如权利要求1所述的方法,其特征在于,所述方法还包括:如果否,则执行标准SR流程响应所述服务请求消息。
如权利要求1所述的方法,其特征在于,所述简化SR流程是:当用户设备有业务要做,并发起服务请求SR流程时,服务网关SGW在本地处理所述SR流程。
如权利要求1或2或3所述的方法,其特征在于,从连接释放流程中获取所述用户设备的当前状态。
如权利要求1或2或3或4所述的方法,其特征在于,所述检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息包括:
检测服务网关中存储的安全向量索引标识符与无线基站通过初始化用户设备消息发送的安全向量索引标识符是否相同,如果相同,则执行简化SR流程响应所述服务请求消息;或
检测用户设备是否从封闭签约用户群组小区接入,并且服务网关中是否具有所述用户设备的封闭签约用户群组签约数据,如果用户设备不从封闭签约用户群组小区接入或者服务网关中具有所述用户设备的封闭签约用户群组签约数据,则执行简化SR流程响应所述服务请求消息;或
检测用户设备是否需要再次鉴权认证,如果不需要再次鉴权认证,则执行简化SR流程响应所述服务请求消息;或
检测服务网关中是否为用户设备设置了合法监听需求标识符,如果没有为用户设置合法监听需求标识符,则执行简化SR流程响应所述服务请求消息;或
检测服务网关中是否为用户设备设置了可达性上报标识符,如果没有为用户设备设置可达性上报标识符,则执行简化SR流程响应所述服务请求消息;或
检测服务网关中是否启动了针对用户设备的寻呼响应定时器且此定时器未超时,如果服务网关中未启动针对用户设备的寻呼响应定时器或者此定时器超时,则执行简化SR流程响应所述服务请求消息。
如权利要求5所述的方法,其特征在于,检测服务网关中存储的安全向量索引标识符与无线基站通过初始化用户设备消息发送的安全向量索引标识符是否相同的步骤具体为:
服务网关获取自身所存储的用户设备上下文数据;
从所述用户设备上下文数据中提取出安全向量索引标识符KSI;
解析无线基站发送的初始化用户设备消息,从所述初始化用户设备消息中提取出用户设备发送的服务请求消息中所包含的KSI;
比较用户设备发送的KSI与服务网关上存储的KSI是否相同。
如权利要求5所述的方法,其特征在于,在所述检测服务网关中存储的安全向量索引标识符与无线基站通过初始化用户设备消息发送的安全向量索引标识符是否相同的步骤之前,所述方法还包括:
在连接释放流程中,服务网关接收移动性管理网元发送的接入承载释放请求消息,所述接入承载释放请求消息中包括安全向量索引标识符;
服务网关存储所述安全向量索引标识符。
如权利要求5所述的方法,其特征在于,所述检测用户设备是否需要再次鉴权认证的步骤包括:
统计用户设备与移动性管理网元之间的信令交互次数;
当所述信令交互次数大于运营商预先设置的最大交互次数上限后,则对所述用户设备进行再次鉴权认证。
如权利要求5所述的方法,其特征在于,在所述检测服务网关中是否为用户设备设置了合法监听需求标识符的步骤之前,所述方法还包括:
监测移动性管理网元是否启动了针对用户设备的合法监听操作;
如果移动性管理网元启动了针对用户设备的合法监听操作,则在服务网关中为用户设备设置合法监听需求标识符。
如权利要求5所述的方法,其特征在于,在所述检测服务网关中是否为用户设备设置了可达性上报标识符的步骤之前,所述方法还包括:
监测是否接收到移动性管理网元转发的用户设备可达性通知请求;
如果接收到移动性管理网元转发的用户设备可达性通知请求,则在服务网关中为用户设备设置可达性上报标识符。
一种服务请求SR流程的执行装置,其特征在于,所述装置包括:
消息接收单元,用于接收无线基站发送的初始化用户设备消息,所述初始化用户设备消息中封装有用户设备发送至无线基站的服务请求消息;
执行单元,用于检测用户设备的当前状态是否满足预先设置的触发策略,如果是,则执行简化SR流程响应所述服务请求消息。
如权利要求11所述的装置,其特征在于,
所述执行单元,还用于如果用户设备的当前状态不满足预先设置的触发策略,则执行标准SR流程响应所述服务请求消息。
如权利要求11或12所述的装置,其特征在于,所述执行单元包括:
标识符检测模块,用于检测服务网关中存储的安全向量索引标识符与无线基站通过初始化用户设备消息发送的安全向量索引标识符是否相同,如果相同,则执行简化SR流程响应所述服务请求消息;或
小区接入检测模块,用于检测用户设备是否从封闭签约用户群组小区接入,并且服务网关中是否具有所述用户设备的封闭签约用户群组签约数据,如果用户设备不从封闭签约用户群组小区接入或者服务网关中具有所述用户设备的封闭签约用户群组签约数据,则执行简化SR流程响应所述服务请求消息;或
再次鉴权检测模块,用于检测用户设备是否需要再次鉴权认证,如果不需要再次鉴权认证,则执行简化SR流程响应所述服务请求消息;或
监听需求检测模块,用于检测服务网关中是否为用户设备设置了合法监听需求标识符,如果没有为用户设备设置合法监听需求标识符,则执行简化SR流程响应所述服务请求消息;或
可达性上报检测模块,用于检测服务网关中是否为用户设备设置了可达性上报标识符,如果没有为用户设备设置可达性上报标识符,则执行简化SR流程响应所述服务请求消息;或
定时器检测模块,用于检测服务网关中是否启动了针对用户设备的寻呼响应定时器且此定时器未超时,如果服务网关中未启动针对用户设备的寻呼响应定时器或者此定时器超,则执行简化SR流程响应所述服务请求消息。
如权利要求13所述的装置,其特征在于,所述标识符检测模块包括:
上下文数据获取子模块,用于获取服务网关自身所存储的用户设备上下文数据;
第一KSI提取子模块,用于从所述用户设备上下文数据中提取出安全向量索引标识符KSI;
第二KSI提取子模块,用于解析无线基站发送的初始化用户设备消息,从所述初始化用户设备消息中提取出用户设备发送的服务请求消息中所包含的KSI;
KSI比较子模块,用于比较用户设备发送的KSI与服务网关上存储的KSI是否相同。
如权利要求13所述的装置,其特征在于,所述装置还包括:
承载释放请求接收单元,用于在连接释放流程中,接收移动性管理网元发送的接入承载释放请求消息,所述接入承载释放请求消息中包括安全向量索引标识符;
安全向量索引存储单元,用于存储所述安全向量索引标识符。
如权利要求13所述的装置,其特征在于,所述再次鉴权检测模块包括:
交互次数统计子模块,用于统计用户设备与移动性管理网元之间的信令交互次数;
再次鉴权判断子模块,用于当所述交互次数统计子模块统计的信令交互次数大于运营商预先设置的最大交互次数上限后,则对所述用户设备进行再次鉴权认证。
如权利要求13所述的装置,其特征在于,所述装置还包括:
合法监听监测单元,用于监测移动性管理网元是否启动了针对用户设备的合法监听操作;
合法监听设置单元,用于当所述合法监听监测单元监测到移动性管理网元启动了针对用户设备的合法监听操作时,则在服务网关中为用户设备设置合法监听需求标识符。
如权利要求13所述的装置,其特征在于,所述装置还包括:
可达性上报监测单元,用于监测是否接收到移动性管理网元转发的用户设备可达性通知请求;
可达性上报设置单元,用于当所述可达性上报监测单元监测到服务网关已经接收到移动性管理网元转发的用户设备可达性通知请求时,则在服务网关中为用户设备设置可达性上报标识符。
一种服务网关,其特征在于,所述服务网关包括如权利要求11至18任一项所述的服务请求SR流程的执行装置。
一种移动网络架构,其特征在于,所述移动网络架构中包括如权利要求19所述的服务网关。
PCT/CN2012/070704 2012-01-21 2012-01-21 一种服务请求sr流程的执行方法、装置及服务网关 WO2013107057A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201280000306.6A CN103548377B (zh) 2012-01-21 2012-01-21 一种服务请求sr流程的执行方法、装置及服务网关
PCT/CN2012/070704 WO2013107057A1 (zh) 2012-01-21 2012-01-21 一种服务请求sr流程的执行方法、装置及服务网关

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/070704 WO2013107057A1 (zh) 2012-01-21 2012-01-21 一种服务请求sr流程的执行方法、装置及服务网关

Publications (1)

Publication Number Publication Date
WO2013107057A1 true WO2013107057A1 (zh) 2013-07-25

Family

ID=48798542

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/070704 WO2013107057A1 (zh) 2012-01-21 2012-01-21 一种服务请求sr流程的执行方法、装置及服务网关

Country Status (2)

Country Link
CN (1) CN103548377B (zh)
WO (1) WO2013107057A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112118600B (zh) * 2020-09-18 2024-05-03 恒安嘉新(北京)科技股份公司 一种5g独立组网sa架构下的流量牵引系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1778136A (zh) * 2003-04-24 2006-05-24 法国电讯 用于控制移动电话请求在umts网络和gsm网络之间传输的方法及相应的控制设备
CN101989948A (zh) * 2009-07-30 2011-03-23 中国电信股份有限公司 宽带接入动态策略控制系统和控制方法
CN102055662A (zh) * 2009-11-06 2011-05-11 中兴通讯股份有限公司 预置路由的确定方法与装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101677470B (zh) * 2008-09-18 2011-12-21 华为技术有限公司 服务请求的处理方法、装置及系统
JP5320618B2 (ja) * 2008-10-02 2013-10-23 株式会社日立製作所 経路制御方法及びアクセスゲートウェイ装置
CN101959192A (zh) * 2009-07-17 2011-01-26 华为技术有限公司 业务处理方法及通信设备
ES2657263T3 (es) * 2010-05-03 2018-03-02 Alcatel Lucent Control de sobrecarga en un sistema de comunicación móvil de paquetes

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1778136A (zh) * 2003-04-24 2006-05-24 法国电讯 用于控制移动电话请求在umts网络和gsm网络之间传输的方法及相应的控制设备
CN101989948A (zh) * 2009-07-30 2011-03-23 中国电信股份有限公司 宽带接入动态策略控制系统和控制方法
CN102055662A (zh) * 2009-11-06 2011-05-11 中兴通讯股份有限公司 预置路由的确定方法与装置

Also Published As

Publication number Publication date
CN103548377B (zh) 2017-01-25
CN103548377A (zh) 2014-01-29

Similar Documents

Publication Publication Date Title
WO2017188787A2 (ko) 무선 통신 시스템에서 기지국에 의해 수행되는 데이터 전달 방법 및 상기 방법을 이용하는 장치
WO2010128773A2 (en) Server for control plane at mobile communication network and method for controlling establishment of connection thereof
WO2017026872A1 (ko) 무선 통신 시스템에서 리모트 ue의 신호 송수신 방법 및 이를 위한 장치
WO2014112836A1 (en) Self-optimizing method for the ue group
WO2011021875A2 (en) Server for control plane at mobile communication network and method for controlling local ip access service
WO2011142568A2 (en) Method and system for positioning mobile station in handover procedure
WO2013168937A1 (en) Method and apparatus for supporting rlf reason detection or handover failure reason detection
CN102685771B (zh) 用户设备接入超时的处理方法、装置
WO2010128786A2 (en) Method for providing connection type information and method for controlling radio resource of home (e)nodeb
WO2015020366A1 (en) Methods, systems and devices for supporting local breakout in small cell architecture
WO2018149368A1 (zh) 一种移动终端VoWiFi通话的处理方法、系统及移动终端
WO2013048189A2 (en) Method for supporting voice service continuity
WO2019066546A1 (en) METHOD AND APPARATUS FOR CONFIGURING A RELEASE CAUSE
WO2015111978A1 (en) Method for controlling, charging, and positioning a ue in a small cell system
WO2013066127A1 (en) Method of initiating a base station and equipment thereof
WO2018143758A1 (ko) 무선 통신 시스템에서 제1 ue와 연결을 가진 제2 ue의 페이징 관련 동작을 수행하는 방법 및 이를 위한 장치
KR100980135B1 (ko) 무선 로컬 네트워크를 umts 터미널 스테이션에접속하기 위한 방법 및 데이터 시스템
WO2014069938A1 (en) Method of automatically adjusting mobility parameter
WO2021206443A1 (ko) 무선 통신 시스템에서 음성 핸드오버 지원 방법 및 장치
WO2015105397A1 (en) Apparatus and method for paging in wireless communication system
WO2016043369A1 (ko) 이종 무선 통신 기술 간의 핸드오버 방법 및 이를 위한 장치
WO2018155901A1 (ko) 무선 통신 시스템에서 amf가 ue의 rm 상태에 관련된 동작을 수행하는 방법 및 이를 위한 장치
WO2012126319A1 (zh) 一种本地访问业务的切换方法及系统
WO2012039585A2 (en) Method for determining relocation process and method for determining handover process
WO2017196014A1 (ko) 이종 네트워크 환경에서 차세대 네트워크 서비스를 제공하는 방법 및 장치

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

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

Country of ref document: EP

Kind code of ref document: A1