WO2011098022A1 - 一种基于m2m应用的会话管理方法、系统和装置 - Google Patents

一种基于m2m应用的会话管理方法、系统和装置 Download PDF

Info

Publication number
WO2011098022A1
WO2011098022A1 PCT/CN2011/070853 CN2011070853W WO2011098022A1 WO 2011098022 A1 WO2011098022 A1 WO 2011098022A1 CN 2011070853 W CN2011070853 W CN 2011070853W WO 2011098022 A1 WO2011098022 A1 WO 2011098022A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
gateway
network element
user equipment
group
Prior art date
Application number
PCT/CN2011/070853
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 JP2012552246A priority Critical patent/JP5603436B2/ja
Priority to EP11741893.9A priority patent/EP2528406B1/en
Publication of WO2011098022A1 publication Critical patent/WO2011098022A1/zh
Priority to US13/572,624 priority patent/US8837326B2/en
Priority to US14/481,341 priority patent/US9271139B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • H2H human to human
  • M2M machine to machine
  • H2H application mainly refers to communication with human communication main body, such as telephone communication
  • M2M application is also called Machine Type Communication (MTC) application, which refers to unattended interaction among multiple network elements.
  • Network communication under the circumstances, such as traffic control and management, factory equipment monitoring, remote meter reading, etc.
  • network operators or users in the industry can manage and control the M2M group as a whole.
  • a remote meter reading application in the power industry can group all the meters in a certain area into a group, the network operator.
  • the power industry users can manage and control the group as a whole; in addition, network operators or users in the industry can also manage and control all M2M user equipments of the same M2M application feature as a whole, for example, the network Operators or users in the industry can manage and control multiple M2M user devices under the same industry user as a whole (constituting a group).
  • Each M2M terminal device under the group can subscribe to the same subscription data, or each M2M terminal device under the group can share a subscription data (group subscription data).
  • the home registration database HLR/HSS
  • the mobility management network element MME/SGSN
  • a session management process such as a bearer modification procedure.
  • the subscription data changes the subscription data of all the user equipments in the group may change, or the scenario in which the group subscription data is shared by all the user equipments in the group, When the group subscription data changes, follow the existing ones.
  • the session management process is initiated based on the user equipment granularity. However, due to the large number of user equipments in the group, a large amount of signaling overhead on the network side may result in signaling congestion on the network side and increase the load on the network.
  • the embodiment of the present invention provides a session management method, system, and device based on an M2M application, so as to implement reasonable utilization of network resources and reduce network load when performing M2M group management.
  • the embodiment of the invention provides a session management method based on an M2M application, and the method includes:
  • the embodiment of the invention provides a session management method based on an M2M application, and the method includes:
  • the embodiment of the invention provides a session management system based on an M2M application, and the system includes:
  • An embodiment of the present invention provides a session management system based on an M2M application, where the system includes: a mobility management network element and a gateway device, where
  • the mobile management network element is configured to learn the gateway device information and the group number information of the group user equipment, and learn to change the group information of the group user equipment; and according to the gateway device information of the group user equipment, The group number information notifies the gateway device to perform bearer change processing on the group user equipment; performing bearer change processing on the group user equipment;
  • the gateway device is configured to learn the mobility management network element information and the group number information of the group user equipment, and learn that the group information of the group user equipment is changed; and the mobile management network element according to the group user equipment The information and group number information notifies the mobility management network element to perform bearer change processing on the group user equipment; and performs bearer change processing on the group user equipment.
  • An embodiment of the present invention provides a mobility management network element, including: a first learning unit, a second learning unit, a first notification unit, and a first execution unit, where
  • the first learning unit is configured to learn gateway device information and group number information of the group user equipment
  • the second learning unit is configured to learn that the group information of the group user equipment changes;
  • the first notification unit is configured to notify the location according to the gateway device information and the group number information of the group user equipment.
  • the gateway device performs bearer change processing on the group user equipment;
  • the first execution unit is configured to perform bearer change processing on the group user equipment.
  • An embodiment of the present invention provides a gateway device, including: a third learned unit, a fourth learned unit, a second notification unit, and a second execution unit, where
  • the third learning unit is configured to learn mobile management network element information and group number information of the group user equipment
  • the fourth learning unit is configured to learn that the group information of the group user equipment is changed;
  • the second notification unit is configured to manage network element information and group number information according to the mobility of the group user equipment. Notifying the mobility management network element to perform bearer change processing on the group user equipment;
  • the second specifying unit is configured to perform bearer change processing on the group user equipment.
  • the technical solution provided by the embodiment of the present invention has the following advantages and features:
  • the gateway device information and the group number information are first known, and the M2M group is shared.
  • the gateway device may be notified to the gateway device to perform bearer change processing on the user equipment according to the learned gateway device information and the group number information, and perform bearer change processing on the group user equipment by itself. Therefore, the overhead of signaling on the network side is reduced, signaling congestion on the network side is avoided, and network load is reduced.
  • FIG. 1 is a flow chart of a session management method based on an M2M application according to an embodiment of the present invention
  • FIG. 2 is a flow chart of a second session management method based on an M2M application according to an embodiment of the present invention
  • FIG. 3 is a flow chart of a third session management method based on an M2M application according to an embodiment of the present invention.
  • FIG. 4 is a flow chart of a fourth session management method based on an M2M application according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a fifth session management method based on an M2M application according to an embodiment of the present invention.
  • FIG. 6 is a flow chart of a sixth session management method based on an M2M application according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a session management system based on an M2M application according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a mobility management network element according to an embodiment of the present invention
  • FIG. 9 is a schematic structural diagram of a gateway device according to an embodiment of the present invention.
  • An embodiment of the present invention provides a session management method based on an M2M application.
  • the process may be as follows:
  • a 101, the gateway device information and the group number information of the group user equipment are obtained;
  • the specific process of obtaining the gateway device information and the group number information may be: When the group user equipment initiates an attach procedure or a PDN connection establishment process or a PDP context activation process,
  • the mobility management network element receives an Attach Request or PDN Connectivity Request or Activate PDP Context Request message sent by the group user equipment;
  • the group may be a user equipment group, a machine to machine (M2M) industry user (MTC User), an M2M application subscription user (MTC Subscriber or MTC Server), or other group composed of multiple devices.
  • M2M machine to machine
  • MTC User machine to machine
  • M2M application subscription user MTC Subscriber or MTC Server
  • the mobility management network element sends a session management request message to the gateway device (eg, the MME/SGSN sends a Create Session Request message to the SGW, and the SGW sends a Create Session Request message to the PGW or the SGSN sends a Create PDP Context Request message to the GGSN), the message
  • the gateway device eg, the MME/SGSN sends a Create Session Request message to the SGW, and the SGW sends a Create Session Request message to the PGW or the SGSN sends a Create PDP Context Request message to the GGSN
  • the gateway device returns the gateway device information and the group number information to the mobility management network element in the session management response message.
  • the specific process may be as follows: The PGW sends a Create Session Response message to the SGW, and the SGW sends the message to the MME/SGSN. Sending a Create Session Response message or the GGSN sends a Create PDP Context Response message to the SGSN, where the message includes the gateway GPRS support node information and the group number information.
  • the mobility management network element (MME/SGSN) and the gateway device (SGW/PGW/GGSN) may store the mobility management network element information, the gateway device information, and the group in a bearer context/PDP context of the group user equipment.
  • Group number information The network device (including the mobility management network element and the gateway device) uniquely identifies the group user equipment by using the mobility management network element information, the gateway device information, and the group number information, where The group user equipment is attached to the same mobility management network element and the same gateway device.
  • the mobile management network element information and the group number information, the gateway device information, and the group number information may be expressed as follows: mode 1, the mobile management network element information, and the group number information may be a mobility management network element identifier + group
  • the identifier such as MME ID/SGSN ID + Group ID
  • gateway device information and group number information may be a gateway device identifier + a group identifier, such as SGW ID/PGW ID/GGSN ID + Group ID.
  • the network device identifier (including the mobility management network element identifier gateway device identifier) may be the following manner but is not limited to the following manner: a globally unique network device identifier, such as a Node ID, where the Node ID may be a globally unique identifier for a network device. , for example, the identity of the mobile management network element
  • MME ID/SGSN ID or the identifier of the gateway device (SGW ID/PGW ID/GGSN ID), or the network device identifier may also be an IP address of the network device or a full domain name of the network device
  • the network device identifier may specifically include: a mobility management network element identifier and a gateway device identifier.
  • the group identifier may be an identifier of a group to which the user equipment belongs (Group ID), or may be an identifier shared by multiple user equipments in the group, for example: an international mobile subscriber identity code
  • the group user equipment is in the active/standby mode.
  • the identity of the master device is as follows: IMSI, MSISDN, IMEI of the master device, Packet Temporary Mobile Subscriber Identity (P-TMSI), and global unique temporary identifier. Globally Unique Temporary Identity (GUTI), etc., or may indicate the identity of a group in other ways, such as: APN.
  • the embodiment of the present invention does not limit the form of the group identification.
  • the mobility management network element information and the group number information may also be a mobility management network element identifier + a resource allocation unit identifier (the resource allocation unit identifier is an identifier assigned by the mobility management network element to the group).
  • the gateway device information and the group number information may also be a gateway device identifier + a resource allocation unit identifier (the resource allocation unit identifier is represented as an identifier assigned by the gateway device to the group).
  • the mobility management network element identifier + resource allocation unit identifier may be composed of one cell, for example, a mobility management network element resource allocation identifier, and the network device identifier + resource allocation unit identifier may also be composed of one cell, such as a network.
  • the device resource allocation identifier is not limited in this embodiment.
  • the resource allocation unit identifier may be in a network device, and the user equipment that uniquely identifies the group, for example, the resource allocation unit identifier may be allocated by the network device (MME/SGSN/SGW/PGW/GGSN). If you can follow the user equipment
  • the specific implementation of the group user equipment corresponding to the network device may be:
  • the network device can allocate the same network device resource allocation identifier to the user equipments in the same group that are accessed under the network device, and the specific implementation is as follows: Mobile Management Network Element (MME/SGSN) Assigning the same resource allocation unit identifier to the user equipment of the same group under which the access network (attached to the mobility management network element), for the same reason, the gateway device
  • SGW/PGW/GGSN assigning the same resource allocation unit identifier to the same group of user equipments under which the access network (establishing a PDN connection or PDP context on the gateway device); or, if the user of the group
  • the device can establish multiple PDN connections (for example, the subscription data contains multiple PDN subscription context information), and the network device can also be based on the PDN connection granularity.
  • the ARP is configured to allocate the resource allocation unit identifier to the user equipment, where the network equipment is the same as the user equipment, and the user equipments in the same group that establish the PDN connection according to the same APN are allocated the same resource allocation unit identifier.
  • the specific implementation is as follows: Mobile management network element
  • MME/SGSN is the same resource allocation unit identifier assigned to the user equipment of the same group that accesses the network (attached to the mobility management network element;) and establishes a PDN connection according to the same APN.
  • the gateway The device is the same group of user equipments that access the network underneath and establish a PDN connection according to the same APN (on which the PDN connection or PDP context is established according to the same APN) Resource allocation unit ID.
  • the mode 3, the mobility management network element information, and the group number information may also be a mobility management network element resource allocation identifier + a group identifier.
  • the mobile management network element resource allocation identifier may be specifically a mobility management network element identifier + a user resource allocation unit.
  • the identifier (the resource allocation unit identifier is represented as an identifier assigned by the mobility management network element to the user equipment).
  • the gateway device information and the group number information may be a gateway device resource allocation identifier + a group identifier, where the mobility management network element resource allocation identifier may be a gateway device identifier + a user resource allocation unit identifier (the user resource allocation unit identifier representation The identifier assigned to the user equipment by the gateway device).
  • the network device resource allocation identifier may identify the user equipment context of the user equipment in a network device (MME/SGSN/SGW/PGW/GGSN).
  • the network device resource allocation identifier may be composed of, but not limited to, the following components: a globally unique network device identifier (for example, a Node ID, where the Node ID may be a globally unique identifier for a network device, such as MME/SGSN/SGW/PGW/GGSN, etc.) and the identifier of the resource allocation unit (in a network node, the identifier of the resource allocation unit may be allocated by the network node, for example, according to the process number or the interface board number or IMSI information, etc.
  • a globally unique network device identifier for example, a Node ID, where the Node ID may be a globally unique identifier for a network device, such as MME/SGSN/SGW/PGW/GGSN, etc.
  • the identifier of the resource allocation unit in a network no
  • the network node can utilize the identity of the resource allocation unit to quickly locate the context of the user equipment).
  • the network device resource allocation identifier may also be composed only of the network device identifier, such as the identifier of the mobility management network element (MME ID/SGSN ID) or the identifier of the gateway device (SGW ID/PGW ID/GGSN ID), The embodiment does not limit the manner in which the network device resource allocation identifier is constructed.
  • a 102 the group information of the group user equipment is changed, and the gateway device is notified to perform the bearer change processing on the group user equipment according to the gateway device information and the group number information of the group user equipment. Performing bearer change processing on the group user equipment.
  • the learning that the group information of the group user equipment is changed may be that the mobility management network element receives an Insert Subscription Data message sent by the home subscription database (HLR/HSS), and the group is learned.
  • the user equipment subscription data is modified; or the mobile management network element receives the Cancel Location message sent by the home registration database (HLR/HSS), and learns that the group user equipment is sold; or the mobility management network element passes the configuration information.
  • the change (for example, by O&M interference) is that the group user equipment group information is changed.
  • the bearer change process may include a bearer modification process, or may include a bearer deactivation process.
  • the bearer deactivation process may further include a separation process. Under the GERAN/UTRAN system, the bearer may be a PDP context.
  • the mobile management network element notifies the gateway device to perform bearer change processing on the group user equipment and perform bearer change processing on the group user equipment according to the gateway device information and the group number information of the group user equipment,
  • the same mobility management network element information and the service gateway information and the packet data network gateway information and group number information may uniquely indicate the group user equipment.
  • the specific process can be:
  • the mobile management network element sends a session management request message to the gateway device to perform bearer change processing on the group user equipment according to the gateway device information and the group number information of the group user equipment learned in the step A 101,
  • the message includes the mobility management network element information and the group number information of the group user equipment.
  • the MME/SGSN sends a Modify Bearer Request/Delete Session Request message to the SGW, where the message sent by the MME/SGSN includes the The mobility management network element information of the group user equipment and the packet data network gateway information and the group number information, and the SGW sends a Modify Bearer Request/Delete Session Request message to the PGW.
  • the message sent by the SGW includes the service gateway information and the mobility management network element information and the group number information of the group user equipment, or the SGSN sends an Update PDP Context Request/Delete PDP Context Request message to the GGSN, and the SGSN sends the message.
  • the message includes the mobility management network element information and the group number information of the group user equipment, and the gateway device learns the mobility management network element information, the gateway information, and the group number information of the group user equipment according to the session management request message ( For example, the PGW learns the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information of the group user equipment according to the message sent by the SGW, or the GGSN sends the information according to the SGSN.
  • the message learns the mobility management network element information, the gateway GPRS support node information, and the group number information of the group user equipment, and performs bearer change processing on the context of the group user equipment according to the learned information,
  • the group user equipment has the same mobility management network element information and the gateway information and the location.
  • Group number information
  • the gateway device returns a session management response message to the mobility management network element (eg, the PGW sends a Modify Bearer Response/Delete Session Response message to the SGW, where the message sent by the PGW includes packet data network gateway information of the group user equipment and The mobile management network element information and the group number information, the SGW sends a Modify Bearer Response/Delete Session Response message to the MME/SGSN, where the message sent by the SGW includes the service gateway information of the group user equipment and the packet data network gateway information.
  • the mobility management network element eg, the PGW sends a Modify Bearer Response/Delete Session Response message to the SGW, where the message sent by the PGW includes packet data network gateway information of the group user equipment and The mobile management network element information and the group number information
  • the SGW sends a Modify Bearer Response/Delete Session Response message to the MME/SGSN, where the message sent by the SGW includes the service gateway information of the group user equipment and the packet data network gateway information.
  • the group number information, or the GGSN sends an Update PDP Context Response/Delete PDP Context Response message to the SGSN, where the message sent by the GGSN includes the gateway GPRS support node information and the group number information of the group user equipment,
  • the mobility management network element learns the mobility management network element information, the gateway information, and the group number information of the group user equipment according to the session management response message.
  • the MME learns the group user equipment according to the message sent by the SGW.
  • the mobile management network element learns the gateway device information of the group user equipment (that is, the gateway management device information that the mobile management network element learns to provide the service for the group user equipment) and the group number information, when the group is known When the group information of the group user equipment is changed, according to the group
  • the gateway device information and the group number information of the group user equipment notify the gateway device to perform bearer change processing on the group user equipment and perform bearer change processing on the group user equipment by using the group granularity, thereby reducing the network.
  • the overhead of side signaling avoids signaling congestion on the network side and reduces network load.
  • the embodiment of the present invention provides a session management method based on an M2M application, and the process is as shown in FIG. 2, which may specifically include:
  • the mobile management network element learns the gateway device information and the group number information of the group user equipment; wherein, in this process, the gateway device can also learn the mobile management network element information and the group number of the group user equipment. information.
  • the gateway device information and the group number information refer to the description in step A 101 of Embodiment 1.
  • the mobile management network element obtains the gateway device information and the group number information of the group user equipment, and the gateway device learns the mobile management network element information and the group number information of the group user equipment, which can be implemented by the following process:
  • the user equipment sends an access request message to the mobility management network element, where the access request message may be an attach request or a PDN Connectivity Request message.
  • the name of the message is not restricted.
  • the mobility management network element learns a group identity of the group user equipment.
  • the mobility management network element may be learned according to the access request message, or may obtain the group identity of the group according to the obtained subscription data, or learn according to the context information of the user equipment or the group.
  • the group identifier of the group the embodiment does not limit how the mobility management network element knows the group identifier.
  • the mobility management network element sends a message to the service gateway to request to create a session.
  • the message may be a Create Session Request message.
  • the name of the message is not limited.
  • the message includes mobility management network element information and group number information of the group user equipment.
  • the serving gateway obtains the mobility management network element information and the group number information of the group user equipment according to the message sent by the mobility management network element in step B102.
  • the service gateway sends a message to the packet data network gateway.
  • the message may be a Create Session Request message, and the name of the message in this embodiment. No restrictions.
  • the message includes mobility management network element information, service gateway information, and group number information of the group user equipment.
  • the packet data network gateway obtains the mobility management network element information, the service gateway information, and the group number information of the group user equipment according to the message sent by the serving gateway in step B103.
  • the packet data network gateway sends a message to the service gateway.
  • the message may be a Create Session Response message.
  • the name of the message is not limited.
  • the message includes packet data network gateway information and group number information of the group user equipment.
  • the serving gateway learns the packet data network gateway information and the group number information of the group user equipment according to the message sent by the packet data network gateway according to the receiving step B 104.
  • the service gateway sends a message to the mobility management network element, and the message may be a Create Session Response message.
  • the name of the message is not limited.
  • the message includes packet data network gateway information, service gateway information, and group number information of the group user equipment.
  • the mobility management network element obtains packet data network gateway information, service gateway information, and group number information of the group user equipment according to the message sent by the serving gateway in step B105.
  • the group information of the group user equipment is changed, and the mobility management network element notifies the gateway device to perform the group user equipment according to the gateway device information and the group number information of the group user equipment. Carrying change processing, and performing bearer change processing on the group user equipment;
  • the mobile management network element notifies the gateway device to perform bearer change processing on the group user equipment and perform bearer change processing on the group user equipment according to the gateway device information and the group number information of the group user equipment,
  • the bearer change process may include a bearer modification process, or may include a bearer deactivation process.
  • the specific process can include:
  • the process 1 the mobile management network element learns that the group information of the group user equipment changes, and the gateway device performs the bearer modification on the group user equipment and performs the bearer modification on the group user equipment.
  • the mobility management network element receives an Insert Subscription Data message sent by the home subscription database (HSS), and learns that the group user is configured.
  • the subscription data changes; or the mobility management NE changes the configuration information (for example,
  • 0&M interference knows when the group information of the group user equipment changes.
  • the mobility management network element initiates a bearer modification process for the group user equipment, and modifies a context of the group user equipment, where the same mobility management network element information and the service gateway information and the The packet data network gateway information and the group number information may uniquely indicate the group user equipment.
  • the mobile management network element sends a message to the service gateway, and the message may be a Modify Bearer Request message.
  • the name of the message is not limited.
  • the message includes the mobility management network element information and the packet data network gateway information and the group number information, or may include the mobility management network element information and the serving gateway information and the packet data network
  • the gateway information and the group number information are not limited in this implementation.
  • the mobile management network element sending the message to the serving gateway may be to have the same mobility management network element information and the service gateway information, the packet data network gateway information, and the group number information.
  • the group user equipment sends a message to the serving gateway instead of sending a plurality of existing modification bearer request messages based on the user equipment granularity.
  • the serving gateway learns, according to the message sent by the mobility management network element, the mobile management network element information, the service gateway information, the packet data network gateway information, and the group number information. Specifically, it can be implemented as follows:
  • the serving gateway may learn the mobility management network element information and the packet from the message. Data network gateway information and the group number information.
  • the service gateway may further match all users accessed according to the learned mobility management network element information and the packet data network gateway information and the group number information.
  • the mobility management network element information and the packet data network gateway information and the group number information in the device context if matched, the service gateway may obtain its own information (service gateway information) according to the user equipment context information;
  • the serving gateway may learn from the message.
  • the mobility management network element information and the service gateway information and the packet data network gateway information and the group number information are described.
  • the service gateway sends a message to the packet data network gateway, where the message may be a Modify Bearer Request message, and the name of the message in this embodiment Said no restrictions.
  • the serving gateway may learn, according to the packet data network gateway information learned in the foregoing step, the packet data network gateway to which the group user equipment is attached.
  • the message sent by the service gateway may include the mobility management network element information, the service gateway information, and the group number information, or may include the mobility management network element information and the service gateway information.
  • the packet data network gateway information and the group number information are not limited in this implementation.
  • the packet data network gateway obtains, according to the message sent by the serving gateway in step B 203, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. Specifically, it can be implemented as follows:
  • the packet data network gateway may learn the mobile management network element from the message. Information and the service gateway information and the group number information, and the packet data network gateway may further match the learned mobility management network element information and the service gateway information and the group number information according to the information If the mobility management network element information and the service gateway and the group number information in the context of all user equipments accessed thereon are matched, the packet data network gateway may obtain its own information (packet data network gateway information) according to the user equipment context information; Alternatively, if the received message includes the mobility management network element information and the serving gateway information and the packet data network gateway information and the group number information, the packet data network gateway may be from the message. Knowing the mobility management network element information and the service gateway information and the packet data network gateway information The group number information.
  • the packet data network gateway updates the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be: the packet data network gateway update owns (saves) the mobile management network element information and the service gateway information learned by the packet data network gateway according to the message sent by the serving gateway in step B 203. And the group user equipment context of the packet data network gateway information and the group number information or the mobility management network element information and the serving gateway information and the group number information.
  • the packet data network gateway to the serving gateway transmits the update completion confirmation message, the message may be contained in a response message 7 father changed (Modify Bearer Response) message, which is not limited to the present embodiment, the name of the message.
  • the message sent by the packet data service gateway may include the mobility management network element information and the packet data network gateway information and the group number information, or may include mobility management network element information and the service gateway.
  • Information and packet data network The network gateway information and the group number information are not limited in this implementation.
  • the serving gateway obtains the mobile management network element information, the service gateway information, the packet data network gateway information, and the group number according to the message sent by the packet data serving gateway according to step B 204.
  • the information can be specifically implemented as follows:
  • the serving gateway may obtain the mobility management network element information from the message. And the packet data network gateway information and the group number information, and the serving gateway may match the learned mobility management network element information and the packet data network gateway information and the group number information according to the learned information. If the mobility management network element information and the packet data network gateway information and the group number information in the context of all user equipments accessed thereon are matched, the service gateway may obtain its own information (service gateway information) according to the user equipment context information;
  • the serving gateway may learn from the message Mobile management network element information and the service gateway information and the packet data network gateway information and the group number information.
  • the serving gateway updates the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be that the serving gateway update owns (saves) the mobility management network element information and the service gateway information learned by the serving gateway according to the message sent by the packet data service gateway according to step B 204, and the service gateway And the group user equipment context of the packet data network gateway information and the group number information or the mobility management network element information and the packet data network gateway information and the group number information.
  • the service gateway sends a message to the mobility management network element to confirm the completion of the update, and the message may be a Modify Bearer Response message.
  • the name of the message is not limited.
  • the message sent by the service gateway may include the service gateway information and the packet data network gateway information and the group number information, or may include the mobility management network element information and the service gateway information and The packet data network gateway information and the group number information are not limited in this implementation.
  • the mobility management network element learns, according to the message sent by the serving gateway in step B 205, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. Specifically, it can be implemented as follows:
  • the mobile management network element may learn the service gateway information, the packet data network gateway information, and the group number information from the message, and further, the moving The management network element may further match the serving gateway information and the grouping in all user equipment contexts accessed thereon according to the learned service gateway information and the packet data network gateway information and the group number information.
  • the data network gateway information and the group number information if they match, the mobility management network element can obtain its own information (mobile management network element information) according to the user equipment context information;
  • the mobility management network element may be from the The mobile management network element information and the service gateway information and the packet data network gateway information and the group number information are known in the message.
  • the mobility management network element updates the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be: the mobility management network element update owns (saves) the mobility management network element information and the service gateway information and the information learned by the foregoing mobility management network element according to the message sent by the service gateway in step B 205. And the group user equipment context of the packet data network gateway information and the group number information or the service gateway information and the packet data network gateway information and the group number information.
  • the process 2 the mobile management network element learns that the group information of the group user equipment changes, notifies the gateway device to perform bearer deactivation on the group user equipment, and performs bearer deactivation on the group user equipment. ;
  • the mobility management network element receives the Insert Subscription Data message sent by the home subscription database (HSS), and learns that the group user equipment subscription data changes (for example, in the original subscription data)
  • HSS home subscription database
  • the APN is not available in the updated subscription data
  • the mobile management network element is informed that the Cancel Location message sent by the Home Signing Data Server (HSS) is received and the message indicates that the group user equipment is rescinded ( withdraw)
  • the mobility management network element learns that the group information of the group user equipment is changed by the change of the configuration information (for example, by O&M interference); or, when the mobility management network element learns that the resource is insufficient, the group needs to be activated.
  • the mobility management network element initiates a bearer deactivation process for the group user equipment, and deactivates a bearer context of the group user equipment, where the same mobility management network element information and the service gateway information are And the packet data network gateway information and the group number information
  • the group user equipment can be uniquely indicated.
  • the bearer deactivation process may further include a separation process.
  • the mobile management network element may send a message to the service gateway, and the message may be a Delete Session Request message.
  • the name of the message is not limited.
  • the message includes the mobility management network element information and the packet data network gateway information and the group number information, or may include the mobility management network element information and the serving gateway information and the packet data network
  • the gateway information and the group number information are not limited in this implementation.
  • the mobile management network element sending the message to the serving gateway may be to have the same mobility management network element information and the service gateway information, the packet data network gateway information, and the group number information.
  • the group user equipment sends a message to the serving gateway instead of sending a plurality of existing delete session request messages based on the user equipment granularity.
  • the serving gateway learns, according to the message sent by the mobility management network element, the mobile management network element information, the service gateway information, the packet data network gateway information, and the group number information, according to the message sent by the mobility management network element. For details, refer to step B 203.
  • the service gateway may send a message to the packet data network gateway, and the message may be a Delete Session Request message.
  • the name of the message is not limited.
  • the message sent by the service gateway may include the mobility management network element information and the service gateway information and the group number information, or may include the mobility management network element information and the service gateway information and The packet data network gateway information and the group number information are not limited in this implementation.
  • the packet data network gateway obtains, according to the message sent by the serving gateway in step B 303, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. For details, refer to step B 204.
  • the packet data network gateway deletes the context information of the group user equipment accessed thereon based on the above information.
  • the specific method may be: the packet data network gateway deletes the mobile management network element information and the service gateway information and the information obtained by the above-mentioned packet data network gateway according to the message sent by the service gateway in step B 303. And the group user equipment context of the packet data network gateway information and the group number information or the mobility management network element information and the service gateway information and the group number information.
  • the packet data network gateway may send a message to the service gateway to confirm that the activation is completed.
  • the message may be a Delete Session Response message, and the name of the message is not limited in this embodiment.
  • the message sent by the packet data network gateway may include the mobility management network element information and the packet data network gateway information and the group number information, or may include mobility management network element information and the service gateway.
  • the information and the packet data network gateway information and the group number information are not limited in this implementation.
  • the serving gateway learns, according to the message sent by the packet data network gateway according to step B 304, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. For details, refer to step B 205.
  • the serving gateway deletes the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be: deleting, by the serving gateway, the mobility management network element information and the service group information obtained by the foregoing service gateway according to the message sent by the packet data network gateway according to step B 304; Data network gateway information and the group number information or the mobile management network element information and the packet data network gateway information and the group user equipment context of the group number information.
  • the service gateway may send a message to the mobility management network element to confirm that the activation is complete.
  • the message may be a Delete Session Response message.
  • the name of the message is not limited.
  • the message sent by the service gateway may include the service gateway information and the packet data network gateway information and the group number information, or may include the mobility management network element information and the service gateway information and The packet data network gateway information and the group number information are not limited in this implementation.
  • the mobility management network element learns, according to the message sent by the serving gateway in step B 305, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. For details, refer to step B 206.
  • the mobility management network element deletes the context information of the group user equipment accessed thereon according to the obtained information.
  • the specific method may be that the mobility management network element deletes the mobile management network element information and the service gateway information and the information that the mobile management network element learns according to the message sent by the serving gateway in step B 305.
  • Example 3 The embodiment of the present invention provides a session management method based on an M2M application, and the process is as shown in FIG. 3, which may specifically include:
  • the mobile management network element learns the gateway device information and the group number information of the group user equipment; wherein, in this process, the gateway device can also learn the mobile management network element information and the group number of the group user equipment. information.
  • the gateway device information and the group number information refer to the description in step A 101 of Embodiment 1.
  • the mobile management network element obtains the gateway device information and the group number information of the group user equipment, and the gateway device learns the mobile management network element information and the group number information of the group user equipment, which can be implemented by the following process:
  • the user equipment sends an access request message to the mobility management network element, where the access request message may be an Active PDP Context Request message, and the name of the access request message is not used in this embodiment. limit.
  • the mobility management network element learns a group identity of the group user equipment.
  • the mobility management network element may be learned according to the access request message, or may obtain the group identity of the group according to the obtained subscription data, or learn according to the context information of the user equipment or the group.
  • the group identifier of the group the embodiment does not limit how the mobility management network element knows the group identifier.
  • the mobility management network element sends a message to the gateway GPRS support node to request activation of the PDP context.
  • the message may be an Active PDP Context Request message.
  • the name of the message is not limited.
  • the message includes mobility management network element information and group number information of the group user equipment.
  • the gateway GPRS support node learns, according to the message sent by the mobility management network element, the mobile management network element information and the group number information of the group user equipment.
  • the gateway GPRS support node sends a message to the mobility management network element to confirm the activation of the PDP context.
  • the message may be an Active PDP Context Response message, and the name of the message is not used in this embodiment. limit.
  • the message includes gateway GPRS support node identification information and group number information of the group user equipment.
  • the group information of the group user equipment is changed, and the mobility management network element notifies the gateway device to perform the group user equipment according to the gateway device information and the group number information of the group user equipment.
  • PDP context change processing and performing PDP context change processing on the group user equipment;
  • the mobility management network element notifies the gateway device to perform PDP context change processing on the group user equipment according to the gateway device information and the group number information of the group user equipment, and performs PDP context change on the group user equipment by itself.
  • the PDP context change process may include a PDP context modification process, or may include a PDP context deactivation process.
  • the specific process can include:
  • the flow management network element learns that the group information of the group user equipment changes, notifies the gateway device to perform PDP context modification on the group user equipment, and performs PDP context modification on the group user equipment by itself. ;
  • the mobility management network element receives the Insert Subscription Data message sent by the home subscription database (HLR), and learns that the group user equipment subscription data changes; or the mobility management network element passes the configuration information.
  • the change for example, by O&M interference
  • O&M interference is known when the group user equipment group information is changed.
  • the mobility management network element initiates a PDP context modification procedure for the group user equipment, and modifies a PDP context of the group user equipment, where the same mobility management network element information and the gateway GPRS support node
  • the information and the group number information may uniquely indicate the group user equipment.
  • the mobile management network element sends a message to the gateway.
  • the GPRS support node requests to update the PDP context, and the message may be an Update PDP Context Request message. This embodiment does not limit the name of the message.
  • the message may include the mobility management network element information and the group number information, or may include the mobility management network element information and the gateway GPRS support node information and the group number information. This is not a limitation.
  • the mobile management network element sends the message to the gateway GPRS support node, which may be the group that has the same mobility management network element information and the gateway GPRS support node information and the group number information.
  • the user equipment sends a message to the gateway GPRS support node instead of transmitting a plurality of existing update PDP context request messages based on the user equipment granularity.
  • the gateway GPRS support node obtains the mobility management network element information, the gateway GPRS support node information, and the group number information according to the message sent by the mobility management network element in step C202, which may specifically pass The following implementation:
  • the gateway GPRS support node may learn the mobility management network element information and the group number information from the message. .
  • the gateway GPRS support node may also be based on the mobile The management network element information and the group number information match the mobility management network element device information and the group number information in the context of all user equipments accessed thereon, and if matched, the gateway GPRS support node may according to the user equipment context information.
  • the gateway GPRS support node may obtain the mobility management network element information and the gateway GPRS support node information and the group number information.
  • the gateway GPRS support node updates the PDP context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be that the gateway GPRS support node is updated to have the mobile management network element information and the group number learned by the gateway GPRS support node according to the message sent by the mobile management network element received in step C 202.
  • the gateway GPRS support node sends a message to the mobility management network element to confirm that the PDP context is updated.
  • the message may be an Update PDP Context Response message.
  • the name of the message is not limited in this embodiment.
  • the message that the gateway GPRS support node sends the message may include the gateway GPRS support node information and the group number information, or may include the mobility management network element information and the gateway GPRS support node information and the group Group number information, this implementation does not limit this.
  • the mobility management network element obtains the mobility management network element information, the gateway GPRS support node information, and the group number information according to the message sent by the gateway GPRS support node in step C 203, which may specifically pass The following implementation:
  • the mobility management network element may learn the gateway GPRS support node information and the group number information from the message. .
  • the mobility management network element may match, according to the learned gateway GPRS support node information and the group number information, gateway GPRS support node information and group number information in all user equipment contexts accessed thereon, If the matching, the mobility management network element can obtain the self-information (mobile management network element information) according to the user equipment context information; or, if the received message includes the mobility management network element information and the gateway GPRS support node information, And the group number information, wherein the mobility management network element can be removed from the The mobile management network element information and the gateway GPRS support node information and the group number information are known in the information.
  • the mobility management network element updates the PDP context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be: the mobility management network element update owns (saves) the gateway GPRS support node information and the group number learned by the foregoing mobility management network element according to the message sent by the gateway GPRS support node in step C 203.
  • the mobility management network element learns that the group user equipment group information changes, notifies the gateway device to perform PDP context deactivation on the group user equipment, and performs a PDP context on the group user equipment by itself. Activate
  • the mobility management network element receives the Insert Subscription Data message sent by the home subscription database (HLR), and learns that the group user equipment group subscription data changes (for example, in the original subscription data)
  • HLR home subscription database
  • the APN is not available in the updated subscription data; or the mobility management network element learns that the group user equipment group information changes through the change of the configuration information (for example, by O&M interference); or, the mobility management network element learns its own resources.
  • the PDP context of the group user equipment needs to be activated.
  • the mobility management network element initiates a PDP context deactivation process for the group user equipment, and deactivates the context of the group user equipment, where the same mobility management network element information and the gateway GPRS support
  • the node information and the group number information may uniquely indicate the group user equipment.
  • the PDP context deactivation process may further include a separation process.
  • the mobile management network element sends a message to the gateway.
  • the GPRS support node requests to delete the PDP context.
  • the message may be a Delete PDP Context Request message.
  • the name of the message is not limited.
  • the message may include the mobility management network element information and the group number information, or may include the mobility management network element information and the gateway GPRS support node information and the group number information. This is not a limitation.
  • the mobile management network element sends the message to the gateway GPRS support node, which may be the group that has the same mobility management network element information and the gateway GPRS support node information and the group number information.
  • the user equipment sends a message to the gateway GPRS support node instead of transmitting a plurality of existing update PDP context deactivation messages based on the user equipment granularity.
  • C 303 The gateway GPRS support node learns the mobility management network element information, the gateway GPRS support node information, and the group number information according to the message sent by the mobility management network element in step C302. For details, refer to Step C 203 is implemented.
  • the gateway GPRS support node deactivates the PDP context of the group user equipment accessed thereon based on the above information.
  • the specific method may be that the gateway GPRS support node deletes the mobile management network element information and the group number that the gateway GPRS support node learns according to the message sent by the mobile management network element in step C302.
  • the gateway GPRS support node may send a message to the mobility management network element to confirm that the PDP context is deactivated.
  • the message may be a Delete PDP Context Response message, and the name of the message is not limited in this embodiment.
  • the message sent by the gateway GPRS support node may include the gateway GPRS support node information and the group number information, or may include the mobility management network element information and the gateway GPRS support node information and the Group number information, this implementation does not limit this.
  • the mobile management network element obtains the mobile management network element information, the gateway GPRS support node information, and the group number information according to the message sent by the gateway GPRS support node in step C303. See step C204.
  • the mobility management network element deactivates the PDP context of the group user equipment accessed thereon based on the learned information.
  • the specific method may be that the mobility management network element deletes the gateway GPRS support node information and the group number that the mobile management network element learns according to the message sent by the gateway GPRS support node in step C 303.
  • the embodiment of the present invention provides a session management method based on an M2M application.
  • the process may be as follows:
  • the process of the mobile management network element information and the group number information of the group user equipment is obtained.
  • the mobility management network element (MME/SGSN) and the gateway device (SGW/PGW/GGSN) may store the mobility management network element information, the gateway device information, and the group in a bearer context/PDP context of the group user equipment. Group number information.
  • the network device (including the mobility management network element and the gateway device) uniquely identifies the group user equipment by using the mobility management network element information, the gateway device information, and the group number information, where The group user equipment is attached to the same mobility management network element and the same gateway device.
  • the gateway device information and the group number information refer to the description in step A101.
  • the group information of the group user equipment is changed, and the mobile management network element is notified to perform the group management by using the mobile management network element information and the group number information of the group user equipment.
  • the change of the group information of the learned group user equipment may be that the gateway device (such as a packet data network gateway or a gateway GRPS support node) receives a PCC message sent by a Policy and Charging Rules Function Entity (PCRF) (for example, Policy and Charging Rules Response message), knowing that the group PCC rule is changed; or the gateway device (for example, a packet data network gateway) receives the message sent by the mobility management network element (for example, the mobility management network element sends a Modify Bearer Command message to the service gateway, the service The gateway sends a Modify Bearer Command message to the packet data network gateway to learn that the QoS of the group user equipment changes; or the gateway device (such as a packet data network gateway or a gateway GRPS support node) changes the configuration information (for example, by O&M interference).
  • PCRF Policy and Charging Rules Function Entity
  • the gateway device for example, a packet data network gateway
  • receives the message sent by the mobility management network element for example, the mobility management network element sends
  • the bearer change processing may include a bearer modification process, or may include a bearer deactivation process.
  • the bearer deactivation process may further include a separation process.
  • the bearer Under the GERAN/UTRAN system, the bearer can be a PDP context.
  • the gateway device notifies the mobility management network element to perform bearer change processing on the group user equipment according to the mobility management network element device information and the group number information of the group user equipment, and performs a bearer on the group user equipment by itself.
  • a change process wherein the same mobility management network element information and the service gateway information and the packet data network gateway information and group number information may uniquely indicate the group user equipment.
  • the specific process can be:
  • the gateway device sends a session management request message to the mobility management network element according to the gateway device information and the group number information of the group user equipment learned in step D101 (eg, the PGW sends an Update Bearer Request/Delete bearer to the SGW).
  • Request message the PGW sends The sent message includes the packet data network gateway information and the mobility management network element information and the group number information of the group user equipment, and the SGW sends an Update Bearer Request/Delete bearer Request message to the MME/SGSN, and the message sent by the SGW.
  • the service gateway information and the packet data network gateway information and the group number information of the group user equipment are included, or the GGSN sends an Update PDP Context Request/Delete PDP Context Request message to the SGSN, where the message sent by the GGSN includes the group
  • the gateway GPRS support node information and the group number information of the user equipment notify the mobile management network element to perform bearer change processing, and the mobility management network element learns the mobility management network element information and the gateway information of the group user equipment according to the session management request message.
  • the group number information (eg, the MME learns the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information of the group user equipment according to the message sent by the SGW, or the SGSN according to the The message sent by the GGSN learns the mobility management network element information, the group user a gateway GPRS support node information and a group number information of the device, performing bearer change processing on a context of the group user equipment according to the learned information, wherein the group user equipment has the same mobile Managing network element information and the gateway information and the group number information;
  • the mobile management network element returns a session management message to the gateway device.
  • the MME/SGSN sends an Update Bearer Response/Delete bearer Response message to the SGW, where the message sent by the MME/SGSN includes the mobility of the group user equipment.
  • the network element information and the group number information, or the SGSN sends an Update PDP Context Response/Delete PDP Context Response message to the GGSN, where the message sent by the SGSN includes the mobility management network element information and the group number information of the group user equipment)
  • the gateway device learns the mobility management network element information, the gateway information, and the group number information of the group user equipment according to the session management request message. For example, the PGW learns the group user equipment according to the message sent by the SGW.
  • the GGSN learns the mobility management network element information, the gateway GPRS support node information, and the group number information of the group user equipment according to the message sent by the SGSN, and is configured to the group user equipment according to the learned information.
  • the gateway device learns the mobility management network element information of the group user equipment (that is, the mobile device management network element information that the gateway device learns to provide the service for the group user equipment) and the group number information, when the group is known
  • the mobile management network element may be notified to the group management device by using the mobility management network element information and the group number information of the group user equipment.
  • the change processing and the bearer change processing of the group user equipment are performed, thereby reducing the overhead of signaling on the network side, avoiding signaling congestion on the network side, and reducing network load.
  • the embodiment of the present invention provides a session management method based on an M2M application, and the process is as shown in FIG. 5, which may specifically include:
  • the gateway device learns the mobility management network element information and the group number information of the group user equipment; wherein, in this process, the mobility management network element can also learn the gateway device information and the group number of the group user equipment. information.
  • the gateway device information and the group number information refer to the description in step A 101 of Embodiment 1.
  • the mobile management network element obtains the gateway device information and the group number information of the group user equipment, and the gateway device learns the mobile management network element information and the group number information of the group user equipment. For details, refer to Step B1 of Embodiment 2 .
  • the group device user group information is changed, and the network device notifies the mobility management network element to the group according to the mobility management network element information of the group user equipment and the group number information.
  • the user equipment performs bearer change processing, and performs bearer change processing on the group user equipment;
  • the network device notifies the mobility management network element to perform bearer change processing on the group user equipment and perform bearer change processing on the group user equipment according to the gateway device information and the group number information of the group user equipment,
  • the bearer change process may include a bearer modification process, or may include a bearer deactivation process.
  • the specific process can include:
  • the gateway device learns that the group user equipment group information changes, notifies the mobility management network element to perform bearer modification on the group user equipment, and performs bearer modification on the group user equipment by itself;
  • the gateway device receives a PCC message (for example, a Policy and Charging Rules Response message) sent by a policy and charging rule function entity (PCRF), and learns that The group user equipment PCC rule is changed; or the gateway device (for example, the packet data network gateway) receives the message sent by the mobility management network element (for example, the mobility management network element sends a Modify Bearer Command message to the service gateway, and the service gateway sends the Modify Bearer Command message again.
  • PCC message for example, a Policy and Charging Rules Response message
  • PCRF policy and charging rule function entity
  • the group user equipment information is changed (for example, the group QoS information is changed); or the gateway device (for example, the packet data network gateway or the gateway GRPS support node) changes the configuration information (for example, 0&M interference) knows that the group user equipment group information is changed.
  • the packet data network gateway initiates a bearer modification process for the group user equipment, and modifies a context of the group user equipment, where the same mobility management network element information and the service gateway information and the
  • the packet data network gateway information and the group number information may uniquely indicate the group user equipment.
  • the packet data network gateway sends a message to the service gateway, and the message may be an Update Bearer Request message.
  • the name of the message is not limited.
  • the message includes the mobility management network element information and the packet data network gateway information and the group number information, or may include the mobility management network element information and the serving gateway information and the packet data network
  • the gateway information and the group number information are not limited in this implementation.
  • the packet data network gateway sending the message to the serving gateway may be to have the same mobility management network element information and the service gateway information, the packet data network gateway information, and the group number information.
  • the group user equipment sends a message to the serving gateway instead of sending a plurality of existing modification bearer request messages based on the user equipment granularity.
  • the serving gateway learns, according to the message sent by the packet data serving gateway, in step E 204, the mobility management network element information, the serving gateway information, the packet data network gateway information, and the group number.
  • the information can be specifically implemented as follows:
  • the serving gateway may obtain the mobility management network element information from the message. And the packet data network gateway information and the group number information, and the serving gateway may match the learned mobility management network element information and the packet data network gateway information and the group number information according to the learned information. If the mobility management network element information and the packet data network gateway information and the group number information in the context of all user equipments accessed thereon are matched, the service gateway may obtain its own information (service gateway information) according to the user equipment context information;
  • the service gateway may learn, by the message, the mobility management network element information, the service gateway information, and the packet data network gateway information and Group number information.
  • the service gateway may send a message to the mobility management network element, and the message may be an Update Bearer Request message.
  • the name of the message is not limited in this embodiment.
  • the message sent by the service gateway may include the packet data network gateway information and the service gateway information and the group number information, or may include the mobility management network element information and the service gateway information and The packet data network gateway information and the group number information are not limited in this implementation.
  • the mobility management network element learns, according to the message sent by the serving gateway in step E 203, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. Specifically, it can be implemented as follows:
  • the mobility management network element may learn the service gateway information from the message and The packet data network gateway information and the group number information, and the mobility management network element may further match, according to the learned service gateway information, the packet data network gateway information, and the group number information. If the service gateway information and the packet data network gateway information and the group number information in the context of all the user equipments accessed thereon are matched, the mobility management network element may obtain the self information according to the user equipment context information ( Mobile management network element information);
  • the mobility management network element may be from the The mobile management network element information and the service gateway information and the packet data network gateway information and the group number information are known in the message.
  • the mobility management network element updates the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be: the mobility management network element update owns (saves) the mobility management network element information and the service gateway information and the information learned by the foregoing mobility management network element according to the message sent by the service gateway in step E 203. And the group user equipment context of the packet data network gateway information and the group number information or the service gateway information and the packet data network gateway information and the group number information.
  • the mobility management network element may send a message to the serving gateway to determine that the update bearer is complete, the message
  • the message may be an Update Bearer Response message, and the name of the message is not limited in this embodiment.
  • the message includes the mobility management network element information and the packet data network gateway information and the group number information, or may include the mobility management network element information and the serving gateway information and the packet data network Gateway information and the group number information, this implementation does not limit this
  • the serving gateway learns, according to the message sent by the mobility management network element in step E204, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. Specifically, it can be implemented as follows:
  • the serving gateway may learn the mobility management network element information and the packet from the message. Data network gateway information and the group number information.
  • the service gateway may further match all users accessed according to the learned mobility management network element information and the packet data network gateway information and the group number information.
  • the mobility management network element information and the packet data network gateway information and the group number information in the device context if matched, the service gateway may obtain its own information (service gateway information) according to the user equipment context information;
  • the serving gateway may learn from the message.
  • the mobility management network element information and the service gateway information and the packet data network gateway information and the group number information are described.
  • the serving gateway updates the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be that the serving gateway update has (save) the mobility management network element information and the service gateway information learned by the serving gateway according to the message sent by the packet data service gateway according to the receiving step E 204, and the And the group user equipment context of the packet data network gateway information and the group number information or the mobility management network element information and the packet data network gateway information and the group number information.
  • the service gateway sends a message to the packet data network gateway to confirm that the bearer update is complete, and the message may be an Update Bearer Response message.
  • the name of the message is not limited in this embodiment.
  • the message sent by the service gateway may include the service gateway information, the mobility management network element information, and the group number information, or may include the mobility management network element information and the service gateway information.
  • the packet data network gateway information and the group number information are not limited in this implementation.
  • the packet data network gateway learns, according to the message sent by the serving gateway in step E 205, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. Specifically, it can be implemented as follows:
  • the packet data network gateway may learn the mobile management network element from the message. Information and the service gateway information and the group number information, and the packet data network gateway may further match the learned mobility management network element information and the service gateway information and the group number information according to the information If the mobility management network element information and the service gateway and the group number information in the context of all user equipments accessed thereon are matched, the packet data network gateway may obtain its own information (packet data network gateway information) according to the user equipment context information;
  • the packet data network gateway may be from the message. Obtaining the mobility management network element information and the serving gateway information and the packet data network gateway information and the group number information.
  • the packet data network gateway updates the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be that the packet data network gateway update owns (saves) the mobile management network element information and the service gateway information learned by the packet data network gateway according to the message sent by the serving gateway in step E 205. And the group user equipment context of the packet data network gateway information and the group number information or the mobility management network element information and the serving gateway information and the group number information.
  • the gateway device learns that the group user equipment group information changes, notifies the mobility management network element to perform bearer deactivation on the group user equipment, and performs bearer deactivation on the group user equipment by itself;
  • the gateway device receives a PCC message (for example, a Policy and Charging Rules Response message) sent by a policy and charging rule function entity (PCRF), for example, learns that the user equipment group PCC rule is changed; or a gateway device (
  • PCC message for example, a Policy and Charging Rules Response message
  • PCF policy and charging rule function entity
  • the packet data network gateway receives the message sent by the mobility management network element (for example, the mobility management network element sends a Modify Bearer Command message to the service gateway, and the service gateway sends a Modify Bearer Command message to the packet data network gateway) to learn the group user.
  • the device information is changed (for example, the APN in the original subscription data is not available in the updated subscription data); or the configuration change of the gateway device (for example, the packet data network gateway or the gateway GRPS support node) (for example, by O&M) Interference) knowing that the group user equipment group information is changed or the like.
  • the gateway device for example, the packet data network gateway or the gateway GRPS support node
  • O&M O&M
  • the packet data network gateway initiates a bearer deactivation process for the group user equipment, and deactivates a context of the group user equipment, where the same mobility management network element information and the service gateway information and The packet data network gateway information and the group number information may uniquely indicate the group user equipment.
  • the bearer deactivation process may further include a separation process.
  • the packet data network gateway sends a message to the serving gateway, and the message may be a Delete Bearer Request message.
  • the name of the message is not limited.
  • the message includes the mobility management network element information and the packet data network gateway information and the group number information, or may include the mobility management network element information and the serving gateway information and the packet data network
  • the gateway information and the group number information are not limited in this implementation.
  • the packet data network gateway sending the message to the serving gateway may be to have the same mobility management network element information and the service gateway information, the packet data network gateway information, and the group number information.
  • the group user equipment sends a message to the serving gateway instead of sending a plurality of existing modification bearer request messages based on the user equipment granularity.
  • the serving gateway according to the message sent by the packet data serving gateway according to step E 304, learns the mobility management network element information, the serving gateway information, the packet data network gateway information, and the group number. For details, refer to step E 203 for implementation.
  • the service gateway may send a message to the mobility management network element, and the message may be a Delete Bearer Request message.
  • the name of the message is not limited.
  • the message sent by the service gateway may include the packet data network gateway information and the service gateway information and the group number information, or may include the mobility management network element information and the service gateway information and The packet data network gateway information and the group number information are not limited in this implementation.
  • the mobility management network element learns, according to the message sent by the serving gateway in step E 303, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. For details, refer to step E 204.
  • the mobility management network element deactivates the context information of the group user equipment accessed thereon according to the obtained information.
  • the specific method may be: the mobility management network element deactivates the mobile management network element information and the service gateway information that are obtained (save) by the foregoing mobility management network element according to the message sent by the service gateway in step E 303.
  • the mobile management network element may send a message to the service gateway to determine the deactivation of the bearer.
  • the message may be that the message may be a Delete Bearer Response message.
  • the name of the message is not limited in this embodiment.
  • the message includes the mobility management network element information and the packet data network gateway information and the group number information, or may include the mobility management network element information and the serving gateway information and the packet data network Gateway information and the group number information, this implementation does not limit this
  • the serving gateway learns, according to the message sent by the mobility management network element, the mobile management network element information, the service gateway information, the packet data network gateway information, and the group number information, according to the message sent by the mobility management network element. For details, see step E 205.
  • the serving gateway deactivates the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be that the serving gateway deactivates the mobile management network element information and the service gateway information and the information that the service gateway learns according to the message sent by the packet data service gateway according to the receiving step E 204.
  • the service gateway sends a message to the packet data network gateway to confirm that the bearer is complete, and the message may be a Delete Bearer Response message.
  • the name of the message is not limited in this embodiment.
  • the message sent by the service gateway may include the service gateway information, the mobility management network element information, and the group number information, or may include the mobility management network element information and the service gateway information.
  • the packet data network gateway information and the group number information are not limited in this implementation.
  • the packet data network gateway learns, according to the message sent by the serving gateway in step E 305, the mobility management network element information, the service gateway information, the packet data network gateway information, and the group number information. For details, refer to step E 206.
  • the packet data network gateway deactivates the context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be: the packet data network gateway deactivates the mobile management network element information and the service gateway information that is owned (saved) by the packet data network gateway according to the message sent by the serving gateway in step E 305. And the packet data Network gateway information and the group number information or the group of user equipment contexts of the mobility management network element information and the service gateway information and the group number information.
  • the embodiment of the present invention provides a session management method based on an M2M application, and the process may be as follows:
  • the gateway device learns the mobility management network element information and the group number information of the group user equipment; wherein, in this process, the mobility management network element can also learn the gateway device information and the group number of the group user equipment. information.
  • the gateway device information and the group number information refer to the description in step A 101 of Embodiment 1.
  • the mobile management network element obtains the gateway device information and the group number information of the group user equipment, and the information about the mobile management network element information and the group number of the group user equipment is obtained by the gateway device. For details, refer to step C1 of Embodiment 3. .
  • the gateway device notifies the mobility management network element to the group user equipment according to the gateway device information of the group user equipment and the group number information.
  • the gateway device notifies the mobility management network element to perform PDP context change processing on the group user equipment according to the mobility management network element information and the group number information of the group user equipment, and performs PDP on the group user equipment by itself.
  • Context change processing where the PDP context change processing may include a PDP context modification process, or may include a PDP context deactivation process.
  • the specific process can include:
  • the gateway device learns that the group user equipment group information changes, notifies the mobility management network element to perform PDP context modification on the group user equipment, and performs PDP context modification on the group user equipment by itself;
  • the gateway device receives a PCC message (for example, a Policy and Charging Rules Response message) sent by a policy and charging rule function entity (PCRF), and learns that the group user equipment PCC rule is changed; or the gateway device receives the mobile Administering the message sent by the network element (for example, the mobility management network element sends an Update Bearer Command message to the gateway device), and learns that the group user equipment information is changed (for example, the group QoS information is changed); or the gateway device changes the configuration information. (For example, by O&M interference), the group user equipment group is known. The group information has changed.
  • PCC message for example, a Policy and Charging Rules Response message
  • PCRF policy and charging rule function entity
  • the gateway device receives the mobile Administering the message sent by the network element (for example, the mobility management network element sends an Update Bearer Command message to the gateway device), and learns that the group user equipment information is changed (for example, the group QoS information is changed); or the gateway device changes the configuration information.
  • the network device (Gateway GPRS Support Node) initiates a PDP context modification procedure for the group user equipment, and modifies a PDP context of the group user equipment, where the same mobility management network element information and the
  • the gateway GPRS support node information and the group number information may uniquely indicate the group user equipment.
  • the gateway GPRS support node sends a message to the mobility management network element to request to update the PDP context, and the message may be an Update PDP Context Request message.
  • the message may include the gateway GPRS support node information and the group number information, or may include the mobility management network element information and the gateway GPRS support node information and the group number information. This is not a limitation.
  • the gateway GPRS support node sends the message to the mobility management network element, which may be the group that has the same mobility management network element information and the gateway GPRS support node information and the group number information.
  • the user equipment sends a message to the gateway GPRS support node instead of transmitting a plurality of existing update PDP context request messages based on the user equipment granularity.
  • the mobile management network element obtains the mobility management network element information, the gateway GPRS support node information, and the group number information according to the message sent by the gateway GPRS support node in step F202, which may specifically pass The following implementation:
  • the mobility management network element may learn the gateway GPRS support node information and the group number information from the message. .
  • the mobility management network element may match, according to the learned gateway GPRS support node information and the group number information, gateway GPRS support node information and group number information in all user equipment contexts accessed thereon, If the matching, the mobility management network element can obtain the self-information (mobile management network element information) according to the user equipment context information; or, if the received message includes the mobility management network element information and the gateway GPRS support node information, And the group number information, the mobility management network element may learn the mobility management network element information and the gateway GPRS support node information and the group number information from the message.
  • the mobility management network element updates the PDP context information of the group user equipment accessed thereon according to the learned information.
  • the specific method may be that the mobility management network element update owns (saves) the foregoing mobile management network element according to the sending by the gateway GPRS support node according to the receiving step F 202.
  • the mobile management network element sends a message to the gateway GPRS support node to confirm the completion of the update PDP context, and the message may be an Update PDP Context Response message.
  • the name of the message is not limited.
  • the mobile management network element may send the message to include the mobility management network element information and the group number information, or may include the mobility management network element information and the gateway GPRS support node information and the group Group number information, this implementation does not limit this.
  • the gateway GPRS support node obtains the mobility management network element information, the gateway GPRS support node information, and the group number information according to the message sent by the mobility management network element in step F 203, which may specifically The following implementation:
  • the gateway GPRS support node may learn the mobility management network element information and the group number information from the message. . In addition, the gateway GPRS support node may further match, according to the mobility management network element information and the group number information, mobility management network element device information and group number information in all user equipment contexts accessed thereon, If matched, the gateway GPRS support node may obtain its own information (gateway GPRS support node information) according to the user equipment context information; or, if the received message includes the mobility management network element information and the gateway GPRS support node information And the group number information, the gateway GPRS support node may learn the mobility management network element information and the gateway GPRS support node information and the group number information from the message.
  • the gateway GPRS support node may learn the mobility management network element information and the gateway GPRS support node information and the group number information from the message.
  • the gateway GPRS support node updates the PDP context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be that the gateway GPRS support node is updated to have the mobile management network element information and the group number that the gateway GPRS support node learns according to the message sent by the mobile management network element in step F 203.
  • Process 2 learning that the group user equipment group information changes, notifying the mobility management network element to perform PDP context deactivation on the group user equipment, and initiating the group user The device performs PDP context deactivation;
  • the gateway device receives a PCC message (for example, a Policy and Charging Rules Response message) sent by the policy and charging rule function entity (PCRF), and learns that the group user equipment PCC rule is changed; or the gateway device receives the mobile Administering the message sent by the network element (for example, the mobility management network element sends an Update Bearer Command message to the gateway device), and learns that the group user equipment information is changed (for example, the group QoS information is changed); or the gateway device changes the configuration information. It is known (for example, by O&M interference) that the group user equipment group information is changed.
  • PCC message for example, a Policy and Charging Rules Response message
  • PCRF policy and charging rule function entity
  • the gateway device receives the mobile Administering the message sent by the network element (for example, the mobility management network element sends an Update Bearer Command message to the gateway device), and learns that the group user equipment information is changed (for example, the group QoS information is changed); or the gateway device changes the configuration information. It is known (for example
  • the network device (Gateway GPRS Support Node) initiates a PDP context deactivation process for the group user equipment, and deactivates a PDP context of the group user equipment, where the same mobility management network element information and
  • the gateway GPRS support node information and the group number information may uniquely indicate the group user equipment.
  • the gateway GPRS support node sends a message to the mobility management network element to request to deactivate the PDP context, and the message may be a Delete PDP Context Request message.
  • the message may include the gateway GPRS support node information and the group number information, or may include the mobility management network element information and the gateway GPRS support node information and the group number information. This is not a limitation.
  • the gateway GPRS support node sends the message to the mobility management network element, which may be the group that has the same mobility management network element information and the gateway GPRS support node information and the group number information.
  • the user equipment sends a message to the gateway GPRS support node instead of sending a plurality of existing delete PDP context request messages based on the user equipment granularity.
  • the mobility management network element obtains the mobility management network element information, the gateway GPRS support node information, and the group number information according to the message sent by the gateway GPRS support node in step F302. For details, refer to Step F 203 is implemented.
  • the mobility management network element deactivates the PDP context information of the group user equipment accessed thereon according to the obtained information.
  • the specific method may be: the mobility management network element deactivates the gateway GPRS support node information that is owned (save) by the foregoing mobility management network element according to the message sent by the gateway GPRS support node in step F 202, and the group.
  • the mobile management network element sends a message to the gateway GPRS support node to confirm the completion of the deactivation of the PDP context, and the message may be a Delete PDP Context Response message.
  • This embodiment does not limit the name of the message.
  • the mobile management network element may send the message to include the mobility management network element information and the group number information, or may include the mobility management network element information and the gateway GPRS support node information and the group Group number information, this implementation does not limit this.
  • Step F 204 the gateway GPRS support node learns the mobility management network element information, the gateway GPRS support node information, and the group number information according to the message sent by the mobility management network element in the receiving step F 303.
  • Step F 204 is implemented as follows:
  • the gateway GPRS support node deactivates the PDP context information of the group user equipment accessed thereon based on the learned information.
  • the specific method may be: the gateway GPRS support node deactivates the mobile management network element information and the group that is owned (saved) by the gateway GPRS support node according to the message sent by the mobile management network element in step F 203.
  • the number information or the mobility management network element information and the group GPRS support node information and the group user equipment PDP context of the group number information.
  • the embodiment of the present invention further provides a session management system based on an M2M application, where the system includes the structure shown in FIG.
  • a mobility management network element 701 and a gateway device 702 where: a mobility management network element 701 is used for Obtaining the gateway device information and the group number information of the group user equipment; learning that the group information of the group user equipment is changed; notifying the gateway device according to the gateway device information and the group number information of the group user equipment 702: Perform bearer change processing on the group user equipment; perform bearer change processing on the group user equipment;
  • the gateway device 702 is configured to learn mobile management network element information and group number information of the group user equipment, and learn to change group information of the group user equipment; and according to the mobile management network of the group user equipment
  • the meta information and the group number information notify the mobility management network element 701 to perform bearer change processing on the group user equipment; and perform bearer change processing on the group user equipment.
  • the M2M application-based session management system provided by this embodiment can be used to implement the M2M application-based session management method according to an embodiment of the present invention.
  • For the session management process of the system refer to the M2M application-based session management method provided by the embodiment of the present invention.
  • a session management system based on M2M application provided by this embodiment, in the system
  • the related information of the M2M group may be uniformly updated according to the group granularity according to the network device resource allocation identification information that is pre-allocated to the group user equipment, thereby reducing network side signaling. Congestion, and correspondingly reduce the network load.
  • the embodiment of the present invention further provides a mobility management network element, where the mobility management network element includes the following structure: a first learning unit 801, a second learning unit 802, a first notification unit 803, and a first execution. Unit 804, wherein
  • the first learning unit 801 is configured to learn gateway device information and group number information of the group user equipment.
  • the second learning unit 802 is configured to learn that the group information of the group user equipment is changed.
  • the first notification unit 803 is configured to notify the gateway according to the gateway device information and the group number information of the group user equipment.
  • the device performs bearer change processing on the group user equipment;
  • the first executing unit 804 is configured to perform bearer change processing on the group user equipment.
  • a mobility management network element provided in this embodiment may be used to implement a session management method based on an M2M application according to an embodiment of the present invention.
  • For the session management process of the mobility management network element refer to the M2M application-based session management method provided by the embodiment of the present invention.
  • the M2M group when the shared subscription data of the M2M group in the system is updated, the M2M group may be allocated according to the network device resource allocation identifier information pre-assigned to the group user equipment.
  • the related information of the group is uniformly updated, thereby reducing the congestion of the signaling on the network side and correspondingly reducing the network load.
  • the embodiment of the present invention further provides a gateway device, which includes the structure shown in FIG. 9: a third learning unit 901, a fourth learning unit 902, a second notification unit 903, and a second executing unit 904, where ,
  • the third learning unit 901 is configured to learn mobile management network element information and group number information of the group user equipment.
  • the fourth learning unit 902 is configured to learn that the group information of the group user equipment is changed.
  • the second notification unit 903 is configured to notify the location according to the mobile management network element information and the group number information of the group user equipment.
  • the mobility management network element performs bearer change processing on the group user equipment;
  • the second executing unit 904 is configured to perform bearer change processing on the group user equipment.
  • a gateway device provided by this embodiment may be used to perform the embodiment of the present invention.
  • Session management method for M2M applications For the session management process of the gateway device, refer to the M2M application-based session management method provided by the embodiment of the present invention.
  • the gateway device When the shared subscription data of the M2M group in the system is updated, the gateway device according to the embodiment may be grouped according to the group identification information of the group user equipment and the network identification information pre-assigned to the group user equipment.
  • the group granularity uniformly updates the related information of the M2M group, thereby reducing the congestion of the network side signaling and correspondingly reducing the network load.
  • the foregoing storage medium includes: a ROM (Read-Only Memory), a RAM (Random Access Memory), a disk, or an optical disk.
  • the medium of the program code includes: a ROM (Read-Only Memory), a RAM (Random Access Memory), a disk, or an optical disk.
  • the above description of the disclosed embodiments enables those skilled in the art to make or use the invention.
  • Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not intended to be limited to the embodiments shown herein, but the broadest scopes

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Computer And Data Communications (AREA)

Description

一种基于 M2M应用的会话管理方法、 系统和装置 本申请要求于 2010年 02月 11 日提交中国专利局、 申请号为 20101011 1544.7, 发明名称为 "一种基于 M2M应用的会话管理方法、 系统 和装置" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及移动通信技术领域， 更具体地说， 涉及一种基于 M2M应用 的会话管理方法、 系统和装置。 背景技术
在现有的通信方式中， 主要存在人到人（H2H， Human to Human )和 机器到机器（M2M， Machine to Machine )两种通信模式。 其中， H2H应用， 主要是指以人为通信主体的通信， 例如电话通信等； 而 M2M应用也称为机 器类型通讯 ( MTC , Machine Type Communications )应用， 是指多个网元 间在无人参与的情况下进行的网络通讯， 例如交通控制和管理、 工厂设备 监控、 远程抄表等。
进一步， 网络运营商或行业内用户可以将 M2M群组作为一个整体进行 管理和控制， 举例来说， 电力行业内的远程抄表应用， 可以将某地地区所 有的电表组成一个群， 网络运营商或电力行业用户可以将该群作为一个整 体进行管理和控制； 另夕卜， 网络运营商或行业内用户也可以将相同 M2M应 用特征的所有 M2M用户设备作为一个整体进行管理和控制， 如， 网络运营 商或行业内用户可以将同一个行业用户下的多个 M2M用户设备作为一个整 体（组成一个群组）进行管理和控制。 对所述群组下的每个 M2M终端设备 可以签约相同的签约数据， 或者所述群组下的每个 M2M终端设备可以共享 一份签约数据 (群组签约数据 ) 。
在人到人通信模式中， 如果一个用户的签约数据发生改变， 则归属地 签约数据库 （HLR/HSS )将发起签约数据修改流程。 根据获知的新的签约 数据， 移动管理网元（MME/SGSN )可发起会话管理流程， 如承载修改流 程。 对于 M2M用户设备组成的群组而言， 如果签约数据发生改变时， 则所 述群组下所有用户设备的签约数据可能发生改变， 或者对于群组下所有用 户设备共享群组签约数据的场景， 群组签约数据发生变化时， 按照现有的 会话管理流程将基于用户设备粒度发起， 但是由于群组下的用户设备的数 目众多， 造成网络侧大量信令开销， 可能导致网络侧出现信令拥塞， 增加 网络的负荷。 发明内容
有鉴于此， 本发明实施例提供一种基于 M2M应用的会话管理方法、 系 统和装置， 以实现进行 M2M群组管理时网络资源的合理利用， 减小网络负 荷。
本发明实施例是这样实现的：
本发明实施例提供了一种基于 M2M应用的会话管理方法， 该方法包 括：
获知群组用户设备的网关设备信息和群组号信息；
获知所述群组用户设备的群组信息发生变更；
根据所述群组用户设备的网关设备信息和群组号信息通知所述网关设 备对所述群组用户设备执行承载变更处理；
对所述群组用户设备执行承载变更处理。
本发明实施例提供了一种基于 M2M应用的会话管理方法， 该方法包 括：
本发明实施例提供了一种基于 M2M应用的会话管理系统， 该系统包 括：
获知群组用户设备的移动管理网元信息和群组号信息；
获知所述群组用户设备的群组信息发生变更；
根据所述群组用户设备的移动管理网元信息和群组号信息通知所述移 动管理网元对所述群组用户设备执行承载变更处理；
对所述群组用户设备执行承载变更处理。
本发明实施例提供了一种基于 M2M应用的会话管理系统， 该系统包 括： 移动管理网元和网关设备， 其中，
所述移动管理网元， 用于获知群组用户设备的网关设备信息和群组号 信息； 获知所述群组用户设备的群组信息发生变更； 根据所述群组用户设 备的网关设备信息和群组号信息通知所述网关设备对所述群组用户设备执 行承载变更处理； 对所述群组用户设备执行承载变更处理； 所述网关设备， 用于获知群组用户设备的移动管理网元信息和群组号 信息； 获知所述群组用户设备的群组信息发生变更； 根据所述群组用户设 备的移动管理网元信息和群组号信息通知所述移动管理网元对所述群组用 户设备执行承载变更处理； 对所述群组用户设备执行承载变更处理。
本发明实施例提供了一种移动管理网元， 包括： 第一获知单元、 第二 获知单元、 第一通知单元和第一执行单元， 其中，
所述第一获知单元， 用于获知群组用户设备的网关设备信息和群组号 信息；
所述第二获知单元， 用于获知所述群组用户设备的群组信息发生变化； 所述第一通知单元， 用于根据所述群组用户设备的网关设备信息和群 组号信息通知所述网关设备对所述群组用户设备执行承载变更处理；
所述第一执行单元， 用于对所述群组用户设备执行承载变更处理。 本发明实施例提供了一种网关设备， 包括： 第三获知单元、 第四获知 单元、 第二通知单元和第二执行单元， 其中，
所述第三获知单元， 用于获知群组用户设备的移动管理网元信息和群 组号信息；
所述第四获知单元， 用于获知所述群组用户设备的群组信息发生变更； 所述第二通知单元， 用于根据所述群组用户设备的移动管理网元信息 和群组号信息通知所述移动管理网元对所述群组用户设备执行承载变更处 理；
所述第二指定单元， 用于对所述群组用户设备执行承载变更处理。 与现有技术相比， 本发明实施例提供的技术方案具有以下优点和特点： 在本发明实施例所提供的技术方案中， 首先获知网关设备信息和群组号信 息， 当 M2M群组的共享信息发生变更时， 可以根据所述获知的网关设备信 息和群组号信息以群组粒度通知所述网关设备对所述用户设备执行承载变 更处理以及自身对所述群组用户设备执行承载变更处理， 从而减少了网络 侧信令的开销， 避免网络侧出现信令拥塞， 减轻网络负荷。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对 实施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员 来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的 附图。
图 1为本发明实施例所提供的一种基于 M2M应用的会话管理方法流程 图；
图 2为本发明实施例所提供的第二种基于 M2M应用的会话管理方法流 程图；
图 3为本发明实施例所提供的第三种基于 M2M应用的会话管理方法流 程图；
图 4为本发明实施例所提供的第四种基于 M2M应用的会话管理方法流 程图；
图 5为本发明实施例所提供的第五种基于 M2M应用的会话管理方法流 程图；
图 6为本发明实施例所提供的第六种基于 M2M应用的会话管理方法流 程图；
图 7为本发明实施例所提供的一种基于 M2M应用的会话管理系统结构 示意图；
图 8为本发明实施例所提供的一种移动管理网元结构示意图； 图 9为本发明实施例所提供的一种网关设备结构示意图。 具体实施方式 下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进 行清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没 有做出创造性劳动前提下所获得的所有其他实施例， 都属于本发明保护的 范围。 实施例 1
本发明实施例提供了一种基于 M2M应用的会话管理方法，流程参见图 1在本实施例中可以包括：
A 101， 获知群组用户设备的网关设备信息和群组号信息；
具体的获知网关设备信息和群组号信息的过程可以是： 在群组用户设备发起的附着流程或者 PDN连接建立流程或者 PDP上下 文激活流程时，
移动管理网元（MME/SGSN )接收所述群组用户设备发送的附着请求 ( Attach Request )或 PDN连接建立清求 ( PDN Connectivity Request )或激 活 PDP上下文清求（ Activate PDP Context Request ) 消息；
获知所述群组用户设备的群组标识（Group ID )， 具体可以通过上述用 户设备发送的请求消息中获取， 或者由移动管理网元从签约数据中获取， 或者根据所述用户设备或所述群组的上下文信息获知所述群组的群组标识 等。 其中所述群组可以是用户设备组、 机器对机器 ( Machine To Machine， 简称 M2M )行业用户 （ MTC User )、 M2M应用签约用户 （ MTC Subscriber 或 MTC Server )或者其他由多个设备组成的群组等， 本发明实施例对此不 作限制。
移动管理网元向网关设备发送会话管理请求消息（如， MME/SGSN向 SGW发送 Create Session Request消息， SGW再向 PGW发送 Create Session Request消息或 SGSN向 GGSN发送 Create PDP Context Request消息）， 所 述消息包括所述群组用户设备的移动管理网元信息和群组号信息；
网关设备在会话管理响应消息中将所述网关设备信息和所述群组号信 息返回给移动管理网元， 具体的可以通过如下流程： PGW 向 SGW发送 Create Session Response消息， SGW再向 MME/SGSN发送 Create Session Response消息或 GGSN向 SGSN发送 Create PDP Context Response消息， 所述消息包括所述网关 GPRS支持节点信息和所述群组号信息。
移动管理网元 （MME/SGSN ) 和网关设备 ( SGW/PGW/GGSN )可以 在群组用户设备的承载上下文 /PDP上下文中存储所述移动管理网元信息、 所述网关设备信息和所述群组号信息。 所述网络设备（含所述移动管理网 元和所述网关设备）通过所述移动管理网元信息、 所述网关设备信息和所 述群组号信息唯一标识所述群组用户设备， 其中， 所述群组用户设备是附 着在相同的所述移动管理网元和相同的所述网关设备中。 其中， 移动管理 网元信息和群组号信息， 网关设备信息和群组号信息的表示形式可以如下： 方式 1、移动管理网元信息和群组号信息可以是移动管理网元标识 +群 组标识， 例如 MME ID/SGSN ID + Group ID, 网关设备信息和群组号信息 可以是网关设备标识 +群组标识， 例如 SGW ID/PGW ID/GGSN ID + Group ID。
其中： 所述网络设备标识 （含移动管理网元标识网关设备标识）可以 是以下方式但不限于以下方式： 全球唯一网络设备标识， 例如 Node ID， 所 述 Node ID可以是全球唯一标识一个网络设备， 如， 移动管理网元的标识
( MME ID/SGSN ID )或网关设备的标识（ SGW ID/PGW ID/GGSN ID )， 或者， 所述网络设备标识还可以是网络设备的 IP地址或网络设备的全域名
( FQDN )， 本实施例对网络设备标识的表示方式不作限制。 在本实施例中， 网络设备标识， 具体的可以包括： 移动管理网元标识和网关设备标识。
其中： 所述群组标识可以是用户设备所属群组的标识（ Group ID )， 还 可以是群组中多个用户设备共享的标识， 例如： 国际移动用户识别码
( International Mobile Subscriber Identification Number , 简称 IMSI )、移动台 国际综合业务数字网号码 ( Mobile Station International Integrated Services Digital Network Number, 简称 MSISDN )、 国际移动设备标识（ International Mobile Equipment Identity, 简称 IMEI )等； 或在群组用户设备在主备组网 方式下， 主设备的标识例如： 主设备的 IMSI、 MSISDN, IMEI、 分组临时 移动用户标识（ Packet Temporary Mobile Subscriber Identity, 简称 P-TMSI )、 全局唯一临时标识（ Globally Unique Temporary Identity, 简称 GUTI )等， 或者可以采用其他方式指示一个群组的标识， 例如： APN等。 本发明实施 例对群组标识的形式不作限制。
方式 2、移动管理网元信息和群组号信息也可以是移动管理网元标识 + 资源分配单元标识 (所述资源分配单元标识表示为该移动管理网元为该群组 分配的标识)。 网关设备信息和群组号信息也可以是网关设备标识 +资源分 配单元标识（所述资源分配单元标识表示为该网关设备为该群组分配的标 识） 。其中，所述移动管理网元标识 +资源分配单元标识可以由一个信元组 成， 例如移动管理网元资源分配标识， 所述网络设备标识 +资源分配单元 标识也可以由一个信元组成， 例如网络设备资源分配标识， 本实施例对此 不做限制。
其中， 所述网络设备标识 （含移动管理网元标识和网关设备标识）表 示方式可以参见方式 1。其中， 所述资源分配单元标识可以在一个网络设备 内， 唯一标识所述群组的用户设备， 例如： 资源分配单元标识可以由所述 网络设备（ MME/SGSN/SGW/PGW/GGSN )分配， 如可以按照用户设备的 速定位到所述网络设备对应的所述群组用户设备的上下文）， 具体实现可以 包括：
网络设备（ MME/SGSN/SGW/PGW/GGSN )可以为在其下接入的同一 群组下的用户设备分配相同的网络设备资源分配标识， 具体实现如下： 移 动管理网元（MME/SGSN )为在其下接入网络（附着在所述移动管理网元） 的同一群组的用户设备分配相同的资源分配单元标识， 同理， 网关设备
( SGW/PGW/GGSN )为在其下接入网络（在所述网关设备上建立 PDN连 接或 PDP上下文） 的同一群组的用户设备分配相同的资源分配单元标识； 或者， 如果群组的用户设备可以建立多个 PDN连接（如， 签约数据中 包含多个 PDN签约上下文信息）， 网络设备还可以根据 PDN 连接粒度
( APN ) 为所述用户设备分配资源分配单元标识， 具体可以为： 网络设备 为在其下接入的， 且根据相同 APN建立 PDN连接的同一群组下的用户设 备分配相同的资源分配单元标识， 具体实现如下： 移动管理网元
( MME/SGSN )为在其下接入网络（附着在所述移动管理网元；)， 且根据相 同 APN建立 PDN连接的同一群组的用户设备分配相同的资源分配单元标 识， 同理， 网关设备（SGW/PGW/GGSN )为在其下接入网络， 且根据相同 APN建立 PDN连接（在所述网关设备上根据相同 APN建立 PDN连接或 PDP上下文） 的同一群组的用户设备分配相同的资源分配单元标识。
方式 3、移动管理网元信息和群组号信息也可以是移动管理网元资源分 配标识 +群组标识； 其中， 移动管理网元资源分配标识具体可以为移动管 理网元标识 +用户资源分配单元标识 (所述资源分配单元标识表示为该移动 管理网元为该用户设备分配的标识)。 网关设备信息和群组号信息可以是网 关设备资源分配标识 +群组标识； 其中， 移动管理网元资源分配标识具体 可以为网关设备标识 +用户资源分配单元标识 (所述用户资源分配单元标识 表示为该网关设备为该用户设备分配的标识)。
其中， 所述网络设备资源分配标识（含移动管理网元标识和网关设备资 源分配标识）可以在一个网络设备 ( MME/SGSN/SGW/PGW/GGSN ) 中标 识用户设备的所述用户设备上下文。 所述网络设备资源分配标识可以由以 下构成但不限于以下构成： 全球唯一网络设备标识 （例如 Node ID, 所述 Node ID 可 以 是 全 球 唯 一 标 识 一 个 网 络 设 备 ， 如 MME/SGSN/SGW/PGW/GGSN等 )和资源分配单元的标识（在一个网络节 点内， 资源分配单元的标识可以由所述网络节点自行分配， 例如按照进程 号或者接口板号或者 IMSI信息等分配， 网络节点可以利用所述资源分配单 元的标识能够快速定位到所述用户设备的上下文）。 或者， 所述网络设备资 源分配标识还可以只由网络设备标识构成，如，移动管理网元的标识（ MME ID/SGSN ID )或网关设备的标识 ( SGW ID/PGW ID/GGSN ID )， 本实施例 对网络设备资源分配标识的构成方式不作限制。
A 102， 获知所述群组用户设备的群组信息发生变更， 根据所述群组用 户设备的网关设备信息和群组号信息通知所述网关设备对所述群组用户设 备执行承载变更处理， 并对所述群组用户设备执行承载变更处理。
其中， 所述获知所述群组用户设备的群组信息发生变更可以是移动管 理网元接收归属地签约数据库 （HLR/HSS )发送的插入签约数据 （Insert Subscription Data ) 消息， 获知所述群组用户设备签约数据发生修改； 或者 移动管理网元接收归属地签约数据库（ HLR/HSS )发送的取消位置（ Cancel Location )消息， 获知所述群组用户设备销户； 或者移动管理网元通过配置 信息的变更（例如通过 0&M干涉 )获知所述群组用户设备群组信息发生变 更。 其中， 所述承载变更处理可以包括承载修改流程， 或者， 可以包括承 载去激活流程。 其中， 承载去激活流程还可以包括分离流程。 在 GERAN/UTRAN系统下， 所述承载可以是 PDP上下文。
移动管理网元根据所述群组用户设备的网关设备信息和群组号信息通 知所述网关设备对所述群组用户设备执行承载变更处理以及自身对所述群 组用户设备执行承载变更处理， 其中， 相同的所述移动管理网元信息和所 述服务网关信息和所述分组数据网络网关信息和群组号信息可以唯一指示 所述群组用户设备。 具体的过程可以是：
移动管理网元根据所述步骤 A 101获知的所述群组用户设备的网关设 备信息和群组号信息向所述网关设备发送会话管理请求消息通知对所述群 组用户设备执行承载变更处理， 所述消息包括所述群组用户设备的移动管 理网元信息和群组号信息 （如， MME/SGSN向 SGW发送 Modify Bearer Request/Delete Session Request消息，所述 MME/SGSN发送的消息包括所述 群组用户设备的移动管理网元信息和分组数据网络网关信息和群组号信 息， SGW再向 PGW发送 Modify Bearer Request/Delete Session Request消息， 所述 SGW发送的消息包括所述群组用户设备的服务网关信息和移动管理 网元信息和群组号信息， 或 SGSN 向 GGSN 发送 Update PDP Context Request/Delete PDP Context Request消息， 所述 SGSN发送的消息包括所述 群组用户设备的移动管理网元信息和群组号信息）， 网关设备根据会话管理 请求消息获知所述群组用户设备的移动管理网元信息和网关信息和群组号 信息 （如， PGW根据所述 SGW发送的所述消息获知所述群组用户设备的 移动管理网元信息、 服务网关信息、 分组数据网络网关信息和群组号信息， 或 GGSN根据所述 SGSN发送的所述消息获知所述群组用户设备的移动管 理网元信息、 网关 GPRS支持节点信息和群组号信息）， 根据上述获知的信 息对所述群组用户设备在其上的上下文执行承载变更处理， 其中， 所述群 组用户设备具有相同的所述移动管理网元信息和所述网关信息和所述群组 号信息；
网关设备返回会话管理响应消息给所述移动管理网元（如， PGW 向 SGW发送 Modify Bearer Response/Delete Session Response消息，所述 PGW 发送的消息包括所述群组用户设备的分组数据网络网关信息和移动管理网 元信息和群组号信息， SGW 再向 MME/SGSN 发送 Modify Bearer Response/Delete Session Response消息， 所述 SGW发送的消息包括所述群 组用户设备的服务网关信息和分组数据网络网关信息和群组号信息， 或 GGSN 向 SGSN发送 Update PDP Context Response/Delete PDP Context Response消息，所述 GGSN发送的消息包括所述群组用户设备的网关 GPRS 支持节点信息和群组号信息）， 所述移动管理网元根据会话管理响应消息获 知所述群组用户设备的移动管理网元信息和网关信息和群组号信息 （如， MME根据所述 SGW发送的所述消息获知所述群组用户设备的移动管理网 元信息 J良务网关信息、分组数据网络网关信息和所述群组号信息，或 SGSN 根据所述 GGSN发送的所述消息获知所述群组用户设备的移动管理网元信 息、 网关 GPRS支持节点信息和群组号信息）， 根据上述获知的信息对所述 群组用户设备在其上的上下文执行承载变更处理， 其中， 所述群组用户设 备具有相同的所述移动管理网元信息和所述网关信息和所述群组号信息。
本发明实施例中，移动管理网元获知群组用户设备的网关设备信息（即 移动管理网元获知为该群组用户设备提供服务的网关设备信息）和群组号 信息， 当获知所述群组用户设备的群组信息发生变更时， 可以根据所述群 组用户设备的网关设备信息和群组号信息以群组粒度通知所述网关设备对 所述群组用户设备进行承载变更处理以及自身对所述群组用户设备进行承 载变更处理， 从而减少了网络侧信令的开销， 避免网络侧出现信令拥塞， 减轻网络负荷。 实施例 2
本发明实施例提供了一种基于 M2M应用的会话管理方法，流程参见图 2， 具体可以包括：
B 1， 移动管理网元获知群组用户设备的网关设备信息和群组号信息； 其中， 在此过程中， 网关设备也可以获知所述群组用户设备的移动管 理网元信息和群组号信息。 其中， 移动管理网元信息和群组号信息， 网关 设备信息和群组号信息的表示形式可以参见实施例 1步骤 A 101描述。 其 中， 移动管理网元获知群组用户设备的网关设备信息和群组号信息， 以及 网关设备获知群组用户设备的移动管理网元信息和群组号信息具体可采用 如下流程实现：
B 101 , 用户设备发送接入请求消息给移动管理网元， 所述接入请求消 息可以是附着请求 ( Attach Request )或者 PDN连接请求（ PDN Connectivity Request ) 消息， 本实施例对所述接入请求消息的名称不做限制。
B 102， 所述移动管理网元获知所述群组用户设备的群组标识。 其中， 所述移动管理网元可以根据所述接入请求消息获知， 或者根据获知的签约 数据中获知所述群组的群组标识， 或者根据所述用户设备或所述群组的上 下文信息获知所述群组的群组标识， 本实施例对移动管理网元如何获知群 组标识不作限制。
所述移动管理网元发送消息给服务网关请求创建会话， 例如， 所述消 息可以是创建会话请求（ Create Session Request ) 消息， 本实施例对所述消 息的名称不做限制。 所述消息包含所述群组用户设备的移动管理网元信息 和群组号信息。
B 103， 服务网关根据接收步骤 B 102所述移动管理网元发送的所述消 息获知所述群组用户设备的移动管理网元信息和群组号信息。
所述服务网关发送消息给分组数据网络网关， 例如， 所述消息可以是 创建会话请求（ Create Session Request ) 消息， 本实施例对所述消息的名称 不做限制。 所述消息包含所述群组用户设备的移动管理网元信息、 服务网 关信息和群组号信息。
B 104， 分组数据网络网关根据接收步骤 B 103所述服务网关发送的所 述消息获知所述群组用户设备的移动管理网元信息、 服务网关信息和群组 号信息。
所述分组数据网络网关发送消息给服务网关， 例如， 所述消息可以是 创建会话响应 （Create Session Response ) 消息， 本实施例对所述消息的名 称不做限制。 所述消息包含所述群组用户设备的分组数据网络网关信息和 群组号信息。
B 105， 服务网关根据接收步骤 B 104所述分组数据网络网关发送的所 述消息获知所述群组用户设备的分组数据网络网关信息和群组号信息。
所述服务网关发送消息给移动管理网元， 所述消息可以是创建会话响 应 （ Create Session Response )消息， 本实施例对所述消息的名称不 #丈限制。 所述消息包括所述群组用户设备的分组数据网络网关信息、 服务网关信息 和群组号信息。
B 106, 移动管理网元根据接收步骤 B 105所述服务网关发送的所述消 息获知所述群组用户设备的分组数据网络网关信息、 服务网关信息和群组 号信息。
B 2, 获知所述群组用户设备的群组信息发生变更， 移动管理网元根据 所述群组用户设备的网关设备信息和群组号信息通知所述网关设备对所述 群组用户设备执行承载变更处理， 并对所述群组用户设备执行承载变更处 理；
移动管理网元根据所述群组用户设备的网关设备信息和群组号信息通 知所述网关设备对所述群组用户设备执行承载变更处理以及自身对所述群 组用户设备执行承载变更处理， 其中， 所述承载变更处理可以包括承载修 改流程， 或者， 可以包括承载去激活流程。 具体的流程可以包括：
流程 1 : 移动管理网元获知所述群组用户设备的群组信息发生变化， 通 知所述网关设备对所述群组用户设备执行承载修改以及自身对所述群组用 户设备执行承载修改；
B 201， 移动管理网元（ MME/SGSN )接收归属地签约数据库 （ HSS ) 发送的插入签约数据 ( Insert Subscription Data )消息， 获知所述群组用户设 备签约数据发生改变； 或者移动管理网元通过配置信息的变更（例如通过
0&M干涉 )获知所述群组用户设备的群组信息发生改变时等。
B 202 , 移动管理网元发起针对所述群组用户设备的承载修改流程， 修 改所述群组用户设备的上下文， 其中， 相同的所述移动管理网元信息和所 述服务网关信息和所述分组数据网络网关信息和所述群组号信息可以唯一 指示所述群组用户设备。
移动管理网元发送消息给服务网关， 所述消息可以是修改承载请求 ( Modify Bearer Request ) 消息， 本实施例对所述消息的名称不 #丈限制。 所 述消息包含所述移动管理网元信息和所述分组数据网络网关信息和所述群 组号信息， 或者， 可以包括所述移动管理网元信息和所述服务网关信息和 所述分组数据网络网关信息和所述群组号信息， 本实施对此不做限制。
其中， 所述移动管理网元发送所述消息给服务网关可以是为拥有相同 的所述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信 息和所述群组号信息的所述群组用户设备发送一条所述消息给所述服务网 关， 而不是基于用户设备粒度发送多条现有修改承载请求消息。
B 203 , 服务网关根据接收步骤 B 202所述移动管理网元发送的所述消 息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 具体可以通过如下实现 ：
若接收到的所述消息只包括所述移动管理网元信息和所述分组数据网 络网关信息和所述群组号信息， 服务网关可以从所述消息中获知移动管理 网元信息和所述分组数据网络网关信息和所述群组号信息， 此外， 服务网 关还可以根据获知的移动管理网元信息和所述分组数据网络网关信息和所 述群组号信息匹配在其上接入的所有用户设备上下文中的移动管理网元信 息和分组数据网络网关信息和群组号信息， 若匹配， 则服务网关可以根据 用户设备上下文信息获知自身信息 （服务网关信息）；
或者， 若接收到的所述消息包括所述移动管理网元信息和所述服务网 关信息和所述分组数据网络网关信息和所述群组号信息， 则服务网关可以 从所述消息中获知所述移动管理网元信息和所述服务网关信息和所述分组 数据网络网关信息和所述群组号信息。
所述服务网关向所述分组数据网络网关发送消息， 所述消息可以是修 改 载请求消息 （ Modify Bearer Request ) 消息， 本实施例对所述消息的名 称不做限制。 其中， 所述服务网关可以根据上述步骤中获知的所述分组数 据网络网关信息获知所述群组用户设备所附着的所述分组数据网络网关。 所述服务网关发送的所述消息可以包含所述移动管理网元信息和所述服务 网关信息和所述群组号信息， 或者， 可以包括所述移动管理网元信息和所 述服务网关信息和所述分组数据网络网关信息和所述群组号信息， 本实施 对此不做限制。
B 204, 分组数据网络网关根据接收步骤 B 203所述服务网关发送的所 述消息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息， 具体可以通过如下实现 ：
若接收到的所述消息只包括所述移动管理网元信息和所述服务网关信 息和所述群组号信息， 则所述分组数据网络网关可以从所述消息中获知所 述移动管理网元信息和所述服务网关信息和所述群组号信息， 此外， 所述 分组数据网络网关还可以根据获知的所述移动管理网元信息和所述服务网 关信息和所述群组号信息匹配在其上接入的所有用户设备上下文中的移动 管理网元信息和服务网关和群组号信息， 若匹配， 则分组数据网络网关可 以根据用户设备上下文信息获知自身信息 （分组数据网络网关信息）； 或者， 若接收到的所述消息包括所述移动管理网元信息和所述服务网 关信息和所述分组数据网络网关信息和所述群组号信息， 则分组数据网络 网关可以从所述消息中获知所述移动管理网元信息和所述服务网关信息和 所述分组数据网络网关信息和所述群组号信息。
分组数据网络网关根据获知的上述信息更新在其上接入的所述群组用 户设备的上下文信息。 具体方法可以是， 分组数据网络网关更新拥有 （保 存）所述分组数据网络网关根据接收步骤 B 203所述服务网关发送的所述 消息获知的所述移动管理网元信息和所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息或所述移动管理网元信息和所述服务网关信 息和所述群组号信息的所述群组用户设备上下文。
所述分组数据网络网关向服务网关发送消息确认完成更新， 所述消息 可以是爹改7 载响应消息 （Modify Bearer Response ) 消息， 本实施例对所 述消息的名称不做限制。 所述分组数据服务网关发送的所述消息可以包含 所述移动管理网元信息和所述分组数据网络网关信息和所述群组号信息， 或者， 可以包括移动管理网元信息和所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息， 本实施对此不做限制。
B 205 , 服务网关根据接收步骤 B 204所述分组数据服务网关发送的所 述消息， 获知所述移动管理网元信息和所述服务网关信息和所述分组数据 网络网关信息和所述群组号信息， 具体可以通过如下实现：
若接收到的所述消息包括所述移动管理网元信息和所述分组数据网络 网关信息和所述群组号信息， 则所述服务网关可以从所述消息中获知所述 移动管理网元信息和所述分组数据网络网关信息和所述群组号信息， 此外， 所述服务网关可以根据获知的所述移动管理网元信息和所述分组数据网络 网关信息和所述群组号信息匹配在其上接入的所有用户设备上下文中的移 动管理网元信息和分组数据网络网关信息和群组号信息， 若匹配， 则服务 网关可以根据用户设备上下文信息获知自身信息 （服务网关信息）；
或者， 若接收到的所述消息所述移动管理网元信息和所述服务网关信 息和所述分组数据网络网关信息和所述群组号信息， 则服务网关可以从所 述消息中获知所述移动管理网元信息和所述服务网关信息和所述分组数据 网络网关信息和所述群组号信息。
服务网关根据获知的上述信息更新在其上接入的所述群组用户设备的 上下文信息。 具体方法可以是， 服务网关更新拥有 （保存）所述服务网关 根据接收步骤 B 204所述分组数据服务网关发送的所述消息获知的所述移 动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息或所述移动管理网元信息和所述分组数据网络网关信息和所述 群组号信息的所述群组用户设备上下文。
所述服务网关向移动管理网元发送消息确认完成更新， 所述消息可以 是爹改 载响应 （ Modify Bearer Response ) 消息， 本实施例对所述消息的 名称不做限制。 所述服务网关发送的所述消息可以包括所述服务网关信息 和所述分组数据网络网关信息和所述群组号信息， 或者， 可以包括所述移 动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息， 本实施对此不做限制。
B 206, 移动管理网元根据接收步骤 B 205所述服务网关发送的所述消 息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 具体可以通过如下实现：
若接收到的所述消息只包括所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 则所述移动管理网元可以从所述消息中获知所 述服务网关信息和所述分组数据网络网关信息和所述群组号信息， 此外， 所述移动管理网元还可以根据获知的所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息匹配在其上接入的所有用户设备上下文中的 所述服务网关信息和所述分组数据网络网关信息和所述群组号信息， 若匹 配， 则移动管理网元可以根据用户设备上下文信息获知自身信息 （移动管 理网元信息）；
或者， 若接收到的所述消息包括所述移动管理网元信息和所述服务网 关信息和所述分组数据网络网关信息和所述群组号信息， 则所述移动管理 网元可以从所述消息中获知所述移动管理网元信息和所述服务网关信息和 所述分组数据网络网关信息和所述群组号信息。
移动管理网元根据获知的上述信息更新在其上接入的所述群组用户设 备的上下文信息。 具体方法可以是， 移动管理网元更新拥有 （保存）上述 移动管理网元根据接收步骤 B 205所述服务网关发送的所述消息获知的所 述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和 所述群组号信息或所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息的所述群组用户设备上下文。
流程 2: 移动管理网元获知所述群组用户设备的群组信息发生变化， 通 知所述网关设备对所述群组用户设备执行承载去激活以及自身对所述群组 用户设备执行承载去激活；
B301 , 移动管理网元（MME/SGSN )接收归属地签约数据库 （ HSS ) 发送的插入签约数据 ( Insert Subscription Data )消息， 获知所述群组用户设 备签约数据发生改变（例如原有签约数据中的 APN在更新的签约数据中不 可用）； 获知移动管理网元接收归属地签约数据服务器（HSS )发送的取消 位置 （Cancel Location ) 消息且所述消息指示所述群组用户设备销户 ( withdraw ); 或者， 移动管理网元通过配置信息的变更（例如通过 0&M 干涉）获知所述群组用户设备的群组信息发生改变； 或者， 移动管理网元 获知自身资源不足时， 需要去激活所述群组用户设备的承载上下文等。
B 302， 移动管理网元发起针对所述群组用户设备的承载去激活流程， 去激活所述群组用户设备的承载上下文， 其中， 相同的所述移动管理网元 信息和所述服务网关信息和所述分组数据网络网关信息和所述群组号信息 可以唯一指示所述群组用户设备。 其中， 所述承载去激活流程还可以包括 分离流程。
移动管理网元可以发送消息给服务网关， 所述消息可以是删除会话请 求（ Delete Session Request ) 消息， 本实施例对所述消息的名称不 #丈限制。 所述消息包含所述移动管理网元信息和所述分组数据网络网关信息和所述 群组号信息， 或者， 可以包括所述移动管理网元信息和所述服务网关信息 和所述分组数据网络网关信息和所述群组号信息， 本实施对此不做限制。
其中， 所述移动管理网元发送所述消息给服务网关可以是为拥有相同 的所述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信 息和所述群组号信息的所述群组用户设备发送一条所述消息给所述服务网 关， 而不是基于用户设备粒度发送多条现有删除会话请求消息。
B 303， 服务网关根据接收步骤 B 302所述移动管理网元发送的所述消 息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 具体可以参见步骤 B 203实现。
所述服务网关可以给分组数据网络网关发送消息， 所述消息可以是删 除会话请求（ Delete Session Request ) 消息， 本实施例对所述消息的名称不 做限制。 所述服务网关发送的所述消息可以包括所述移动管理网元信息和 所述服务网关信息和所述群组号信息， 或者， 可以包括所述移动管理网元 信息和所述服务网关信息和所述分组数据网络网关信息和所述群组号信 息， 本实施对此不做限制。
B 304， 分组数据网络网关根据接收步骤 B 303所述服务网关发送的所 述消息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息， 具体可以参见步骤 B 204实现。
分组数据网络网关根据上述信息删除在其上接入的所述群组用户设备 的上下文信息。 具体方法可以是， 分组数据网络网关删除拥有 （保存）上 述分组数据网络网关根据接收步骤 B 303所述服务网关发送的所述消息获 知的所述移动管理网元信息和所述服务网关信息和所述分组数据网络网关 信息和所述群组号信息或所述移动管理网元信息和所述服务网关信息和所 述群组号信息的所述群组用户设备上下文。
所述分组数据网络网关可以给服务网关发送消息确认去激活完成， 所 述消息可以是删除会话响应 （Delete Session Response ) 消息， 本实施例对 所述消息的名称不做限制。 所述分组数据网络网关发送的所述消息可以包 含所述移动管理网元信息和所述分组数据网络网关信息和所述群组号信 息， 或者， 可以包括移动管理网元信息和所述服务网关信息和所述分组数 据网络网关信息和所述群组号信息， 本实施对此不做限制。
B 305， 服务网关根据接收步骤 B 304所述分组数据网络网关发送的所 述消息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息， 具体可以参见步骤 B 205实现。
服务网关根据获知的上述信息删除在其上接入的所述群组用户设备的 上下文信息。 具体方法可以是， 服务网关删除拥有 （保存）上述服务网关 根据接收步骤 B 304所述分组数据网络网关发送的所述消息获知的所述移 动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息或所述移动管理网元信息和所述分组数据网络网关信息和所述 群组号信息的所述群组用户设备上下文。
所述服务网关可以给移动管理网元发消息确认去激活完成， 所述消息 可以是删除会话请求消息 （Delete Session Response ) 消息， 本实施例对所 述消息的名称不做限制。 所述服务网关发送的所述消息可以包含所述服务 网关信息和所述分组数据网络网关信息和所述群组号信息， 或者， 可以包 括所述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信 息和所述群组号信息， 本实施对此不做限制。
B 306, 移动管理网元根据接收步骤 B 305所述服务网关发送的所述消 息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 具体可以参见步骤 B 206实现。
移动管理网元根据获知的上述信息删除在其上接入的所述群组用户设 备的上下文信息。 具体方法可以是， 移动管理网元删除拥有 （保存）上述 移动管理网元根据接收步骤 B 305所述服务网关发送的所述消息获知的所 述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和 所述群组号信息或所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息的所述群组用户设备上下文。 实施例 3 本发明实施例提供了一种基于 M2M应用的会话管理方法，流程参见图 3， 具体可以包括：
C 1， 移动管理网元获知群组用户设备的网关设备信息和群组号信息； 其中， 在此过程中， 网关设备也可以获知所述群组用户设备的移动管 理网元信息和群组号信息。 其中， 移动管理网元信息和群组号信息， 网关 设备信息和群组号信息的表示形式可以参见实施例 1步骤 A 101描述。 其 中， 移动管理网元获知群组用户设备的网关设备信息和群组号信息， 以及 网关设备获知群组用户设备的移动管理网元信息和群组号信息具体可采用 如下流程实现：
C 101 , 用户设备发送接入请求消息给移动管理网元， 所述接入请求消 息可以是激活 PDP上下文请求（Active PDP Context Request ) 消息， 本实 施例对所述接入请求消息的名称不做限制。
C 102， 所述移动管理网元获知所述群组用户设备的群组标识。 其中， 所述移动管理网元可以根据所述接入请求消息获知， 或者根据获知的签约 数据中获知所述群组的群组标识， 或者根据所述用户设备或所述群组的上 下文信息获知所述群组的群组标识， 本实施例对移动管理网元如何获知群 组标识不作限制。
所述移动管理网元发送消息给网关 GPRS支持节点请求激活 PDP上下 文， 例如， 所述消息可以是激活 PDP 上下文请求 （Active PDP Context Request ) 消息， 本实施例对所述消息的名称不做限制。 所述消息包含所述 群组用户设备的移动管理网元信息和群组号信息。
C 103， 网关 GPRS支持节点根据接收步骤 C 102所述移动管理网元发 送的所述消息获知所述群组用户设备的移动管理网元信息和群组号信息。
所述网关 GPRS支持节点发送消息给所述移动管理网元确认激活 PDP 上下文， 例如， 所述消息可以是激活 PDP上下文响应 ( Active PDP Context Response )消息， 本实施例对所述消息的名称不做限制。 所述消息包含所述 群组用户设备的网关 GPRS支持节点标识信息和群组号信息。
C 2, 获知所述群组用户设备的群组信息发生变更， 移动管理网元根据 所述群组用户设备的网关设备信息和群组号信息通知所述网关设备对所述 群组用户设备执行 PDP上下文变更处理， 并对所述群组用户设备执行 PDP 上下文变更处理； 移动管理网元根据所述群组用户设备的网关设备信息和群组号信息通 知所述网关设备对所述群组用户设备执行 PDP上下文变更处理以及自身对 所述群组用户设备执行 PDP上下文变更处理， 其中， 所述 PDP上下文变更 处理可以包括 PDP上下文修改流程， 或者， 可以包括 PDP上下文去激活流 程。 具体的流程可以包括：
流程 1 : 移动管理网元获知所述群组用户设备的群组信息发生变化， 通 知所述网关设备对所述群组用户设备执行 PDP上下文修改以及自身对所述 群组用户设备执行 PDP上下文修改；
C 201 , 移动管理网元（SGSN )接收归属地签约数据库 （HLR )发送 的插入签约数据 ( Insert Subscription Data )消息， 获知所述群组用户设备签 约数据发生改变； 或者移动管理网元通过配置信息的变更（例如通过 0&M 干涉）获知所述群组用户设备群组信息发生改变时等。
C 202,移动管理网元发起针对所述群组用户设备的 PDP上下文修改流 程， 修改所述群组用户设备的 PDP上下文， 其中， 相同的所述移动管理网 元信息和所述网关 GPRS 支持节点信息和所述群组号信息可以唯一指示所 述群组用户设备。
移动管理网元发送消息给网关 GPRS支持节点请求更新 PDP上下文， 所述消息可以是更新 PDP上下文请求（ Update PDP Context Request )消息， 本实施例对所述消息的名称不做限制。 所述消息可以包括所述移动管理网 元信息和所述群组号信息， 或者， 可以包括所述移动管理网元信息和所述 网关 GPRS支持节点信息和所述群组号信息， 本实施对此不做限制。
其中， 所述移动管理网元发送所述消息给网关 GPRS 支持节点可以是 为拥有相同的所述移动管理网元信息和所述网关 GPRS 支持节点信息和所 述群组号信息的所述群组用户设备发送一条所述消息给所述网关 GPRS 支 持节点，而不是基于用户设备粒度发送多条现有更新 PDP上下文请求消息。
C 203， 网关 GPRS支持节点根据接收步骤 C 202所述移动管理网元发 送的所述消息获知所述移动管理网元信息和所述网关 GPRS 支持节点信息 和所述群组号信息， 具体可以通过如下实现 ：
若接收到的所述消息只包括所述移动管理网元信息和所述群组号信 息， 则网关 GPRS 支持节点可以从所述消息中获知所述移动管理网元信息 和所述群组号信息。 此外， 所述网关 GPRS 支持节点还可以根据所述移动 管理网元信息和所述群组号信息匹配在其上接入的所有用户设备上下文中 的移动管理网元设备信息和群组号信息， 若匹配， 则网关 GPRS 支持节点 可以根据用户设备上下文信息获知自身信息 （网关 GPRS支持节点信息）； 或者， 若接收到的所述消息包括所述移动管理网元信息和所述网关 GPRS支持节点信息和所述群组号信息，则网关 GPRS支持节点可以从所述 消息中获知所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述 群组号信息。
网关 GPRS 支持节点根据获知的上述信息更新在其上接入的所述群组 用户设备的 PDP上下文信息。 具体方法可以是， 网关 GPRS支持节点更新 拥有 （保存）上述网关 GPRS支持节点根据接收步骤 C 202所述移动管理 网元发送的所述消息获知的所述移动管理网元信息和所述群组号信息或所 述移动管理网元信息和所述网关 GPRS 支持节点信息和所述群组号信息的 所述群组用户设备 PDP上下文。
所述网关 GPRS支持节点向移动管理网元发送消息确认完成更新 PDP 上下文， 所述消息可以是更新 PDP 上下文响应 （Update PDP Context Response ) 消息， 本实施例对所述消息的名称不做限制。 所述网关 GPRS 支持节点发送所述消息可以包含所述网关 GPRS 支持节点信息和所述群组 号信息， 或者， 可以包括所述移动管理网元信息和所述网关 GPRS 支持节 点信息和所述群组号信息， 本实施对此不做限制。
C 204, 移动管理网元根据接收步骤 C 203所述网关 GPRS支持节点发 送的所述消息获知所述移动管理网元信息和所述网关 GPRS 支持节点信息 和所述群组号信息， 具体可以通过如下实现 ：
若接收到的所述消息只包括所述网关 GPRS 支持节点信息和所述群组 号信息， 则移动管理网元可以从所述消息中获知所述网关 GPRS 支持节点 信息和所述群组号信息。 此外， 所述移动管理网元可以根据获知的所述网 关 GPRS 支持节点信息和所述群组号信息匹配在其上接入的所有用户设备 上下文中的网关 GPRS 支持节点信息和群组号信息， 若匹配， 则移动管理 网元可以根据用户设备上下文信息获知自身信息 （移动管理网元信息）； 或者， 若接收到的所述消息包括所述移动管理网元信息和所述网关 GPRS支持节点信息和所述群组号信息，则所述移动管理网元可以从所述消 息中获知所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述群 组号信息。
移动管理网元根据获知的上述信息更新在其上接入的所述群组用户设 备的 PDP上下文信息。 具体方法可以是， 移动管理网元更新拥有 （保存） 上述移动管理网元根据接收步骤 C 203所述网关 GPRS支持节点发送的所 述消息获知的所述网关 GPRS 支持节点信息和所述群组号信息或所述移动 管理网元信息和所述网关 GPRS 支持节点信息和所述群组号信息的所述群 组用户设备 PDP上下文。
流程 2: 移动管理网元获知所述群组用户设备群组信息发生变化， 通知 所述网关设备对所述群组用户设备执行 PDP上下文去激活以及自身对所述 群组用户设备执行 PDP上下文去激活；
C 301， 移动管理网元（SGSN )接收归属地签约数据库 （HLR )发送 的插入签约数据 ( Insert Subscription Data )消息， 获知所述群组用户设备群 组签约数据发生改变（例如原有签约数据中的 APN在更新的签约数据中不 可用）； 或者移动管理网元通过配置信息的变更（例如通过 0&M干涉）获 知所述群组用户设备群组信息发生改变； 或者， 移动管理网元获知自身资 源不足时， 需要去激活所述群组用户设备的 PDP上下文等。
C 302，移动管理网元发起针对所述群组用户设备的 PDP上下文去激活 流程， 去激活所述群组用户设备的上下文， 其中， 相同的所述移动管理网 元信息和所述网关 GPRS 支持节点信息和所述群组号信息可以唯一指示所 述群组用户设备。其中，所述 PDP上下文去激活流程还可以包括分离流程。
移动管理网元发送消息给网关 GPRS支持节点请求删除 PDP上下文， 所述消息可以是删除 PDP上下文请求（ Delete PDP Context Request ) 消息， 本实施例对所述消息的名称不做限制。 所述消息可以包括所述移动管理网 元信息和所述群组号信息， 或者， 可以包括所述移动管理网元信息和所述 网关 GPRS支持节点信息和所述群组号信息， 本实施对此不做限制。
其中， 所述移动管理网元发送所述消息给网关 GPRS 支持节点可以是 为拥有相同的所述移动管理网元信息和所述网关 GPRS 支持节点信息和所 述群组号信息的所述群组用户设备发送一条所述消息给所述网关 GPRS 支 持节点， 而不是基于用户设备粒度发送多条现有更新 PDP上下文去激活消 息。 C 303， 网关 GPRS支持节点根据接收步骤 C 302所述移动管理网元发 送的所述消息获知所述移动管理网元信息和所述网关 GPRS 支持节点信息 和所述群组号信息， 具体可以参见步骤 C 203实现。
网关 GPRS 支持节点根据上述信息去激活在其上接入的所述群组用户 设备的 PDP上下文。 具体方法可以是， 网关 GPRS支持节点删除拥有 （保 存）上述网关 GPRS支持节点根据接收步骤 C 302所述移动管理网元发送 的所述消息获知的所述移动管理网元信息和所述群组号信息或所述移动管 理网元信息和所述网关 GPRS 支持节点信息和所述群组号信息的所述群组 用户设备 PDP上下文。
所述网关 GPRS 支持节点可以给移动管理网元发送消息确认完成去激 活 PDP上下文， 所述消息可以是删除 PDP上下文响应（ Delete PDP Context Response ) 消息， 本实施例对所述消息的名称不做限制。 所述网关 GPRS 支持节点发送的所述消息可以包含所述网关 GPRS 支持节点信息和所述群 组号信息， 或者， 可以包括所述移动管理网元信息和所述网关 GPRS 支持 节点信息和所述群组号信息， 本实施对此不做限制。
C 304，移动管理网元根据接收步骤 C 303所述网关 GPRS支持节点发 送的所述消息， 获知所述移动管理网元信息和所述网关 GPRS 支持节点信 息和所述群组号信息， 具体可以参见步骤 C 204。
移动管理网元根据获知的上述信息去激活在其上接入的所述群组用户 设备的 PDP上下文。 具体方法可以是， 移动管理网元删除拥有 （保存）上 述移动管理网元根据接收步骤 C 303所述网关 GPRS支持节点发送的所述 消息获知的所述网关 GPRS 支持节点信息和所述群组号信息或所述移动管 理网元信息和所述网关 GPRS 支持节点信息和所述群组号信息的所述用户 设备 PDP上下文。 实施例 4
本发明实施例提供了一种基于 M2M应用的会话管理方法，流程参见图 4在本实施例中可以包括：
D 101， 获知群组用户设备的移动管理网元信息和群组号信息； 其中， 具体的获知群组用户设备的移动管理网元信息和群组号信息的 过程可以参见步骤 A 101中描述。 移动管理网元 （MME/SGSN ) 和网关设备 ( SGW/PGW/GGSN )可以 在群组用户设备的承载上下文 /PDP上下文中存储所述移动管理网元信息、 所述网关设备信息和所述群组号信息。 所述网络设备（含所述移动管理网 元和所述网关设备）通过所述移动管理网元信息、 所述网关设备信息和所 述群组号信息唯一标识所述群组用户设备， 其中， 所述群组用户设备是附 着在相同的所述移动管理网元和相同的所述网关设备中。
其中， 移动管理网元信息和群组号信息， 网关设备信息和群组号信息 的表示形式可以参见步骤 A 101中描述。
D 102, 获知所述群组用户设备的群组信息发生变更， 根据所述群组用 户设备的移动管理网元信息和群组号信息通知所述移动管理网元对所述群 组用户设备执行承载变更处理， 并对所述群组用户设备执行承载变更处理。
其中，所述获知群组用户设备的群组信息发生变更可以是网关设备（例 如分组数据网络网关或网关 GRPS 支持节点）接收策略与计费规则功能实 体 ( PCRF )发送的 PCC消息 (例如 Policy and Charging Rules Response消 息）， 获知所述群组 PCC规则发生变更； 或者网关设备（例如分组数据网络 网关）接收移动管理网元发送的消息（例如移动管理网元发送 Modify Bearer Command消息给服务网关， 服务网关再发送 Modify Bearer Command消息 给分组数据网络网关）， 获知所述群组用户设备 QoS发生变更； 或者网关设 备（例如分组数据网络网关或网关 GRPS 支持节点）通过配置信息的变更 (例如通过 0&M干涉）获知群组信息发生变更等。 其中， 所述承载变更处 理可以包括承载修改流程， 或者， 可以包括承载去激活流程。 其中， 所述 承载去激活流程还可以包括分离流程。 在 GERAN/UTRAN系统下， 所述承 载可以是 PDP上下文。
网关设备根据所述群组用户设备的移动管理网元设备信息和群组号信 息通知所述移动管理网元对所述群组用户设备执行承载变更处理以及自身 对所述群组用户设备执行承载变更处理， 其中， 相同的所述移动管理网元 信息和所述服务网关信息和所述分组数据网络网关信息和群组号信息可以 唯一指示所述群组用户设备。 具体的过程可以是：
网关设备根据所述步骤 D 101获知的所述群组用户设备的网关设备信 息和群组号信息向所述移动管理网元发送会话管理请求消息（如， PGW向 SGW发送 Update Bearer Request/Delete bearer Request消息， 所述 PGW发 送的消息包括所述群组用户设备的分组数据网络网关信息和移动管理网元 信息和群组号信息， SGW 再向 MME/SGSN 发送 Update Bearer Request/Delete bearer Request消息， 所述 SGW发送的消息包括所述群组用 户设备的服务网关信息和分组数据网络网关信息和群组号信息， 或 GGSN 向 SGSN发送 Update PDP Context Request/Delete PDP Context Request消息， 所述 GGSN发送的消息包括所述群组用户设备的网关 GPRS支持节点信息 和群组号信息）通知移动管理网元执行承载变更处理， 移动管理网元根据 会话管理请求消息获知所述群组用户设备的移动管理网元信息和网关信息 和群组号信息 （如， MME根据所述 SGW发送的所述消息获知所述群组用 户设备的移动管理网元信息、 服务网关信息、 分组数据网络网关信息和群 组号信息， 或 SGSN根据所述 GGSN发送的所述消息获知所述移动管理网 元信息、 所述群组用户设备的网关 GPRS支持节点信息和群组号信息）， 根 据上述获知的信息对所述群组用户设备在其上的上下文执行承载变更处 理， 其中， 所述群组用户设备具有相同的所述移动管理网元信息和所述网 关信息和所述群组号信息；
移动管理网元网元返回会话管理消息给所述网关设备（如， MME/SGSN 向 SGW发送 Update Bearer Response/Delete bearer Response消息， 所述 MME/SGSN发送的消息包括所述群组用户设备的移动管理网元信息和分组 数据网络网关信息和群组号信息， SGW 再向 PGW 发送 Update Bearer Response/Delete bearer Response消息， 所述 SGW发送的消息包括所述群组 用户设备的服务网关信息和移动管理网元信息和群组号信息， 或 SGSN向 GGSN发送 Update PDP Context Response/Delete PDP Context Response消 息， 所述 SGSN发送的消息包括所述群组用户设备的移动管理网元信息和 群组号信息）， 网关设备根据会话管理请求消息获知所述群组用户设备的移 动管理网元信息和网关信息和群组号信息 （如， PGW根据所述 SGW发送 的所述消息获知所述群组用户设备的移动管理网元信息、 服务网关信息、 分组数据网络网关信息和群组号信息， 或 GGSN根据所述 SGSN发送的所 述消息获知所述群组用户设备的移动管理网元信息、 网关 GPRS 支持节点 信息和群组号信息）， 根据上述获知的信息对所述群组用户设备在其上的上 下文执行承载变更处理， 其中， 所述群组用户设备具有相同的所述移动管 理网元信息和所述网关信息和所述群组号信息； 本发明实施例中，网关设备获知群组用户设备的移动管理网元信息（即 网关设备获知为该群组用户设备提供服务的移动管理网元信息）和群组号 信息， 当获知所述群组用户设备的群组信息发生变更时， 可以根据所述群 组用户设备的移动管理网元信息和群组号信息以群组粒度通知所述移动管 理网元对所述群组用户设备进行承载变更处理以及自身对所述群组用户设 备进行承载变更处理， 从而减少了网络侧信令的开销， 避免网络侧出现信 令拥塞， 减轻网络负荷。 实施例 5
本发明实施例提供了一种基于 M2M应用的会话管理方法，流程参见图 5， 具体可以包括：
E 1， 网关设备获知群组用户设备的移动管理网元信息和群组号信息； 其中， 在此过程中， 移动管理网元也可以获知所述群组用户设备的网 关设备信息和群组号信息。 其中， 移动管理网元信息和群组号信息， 网关 设备信息和群组号信息的表示形式可以参见实施例 1步骤 A 101描述。 其 中， 移动管理网元获知群组用户设备的网关设备信息和群组号信息， 以及 网关设备获知群组用户设备的移动管理网元信息和群组号信息具体可参见 实施例 2步骤 B 1实现。
E 2, 获知所述群组用户设备群组信息发生变更， 网络设备根据所述群 组用户设备的移动管理网元信息和所述群组号信息通知所述移动管理网元 对所述群组用户设备执行承载变更处理， 并对所述群组用户设备执行承载 变更处理；
网络设备根据所述群组用户设备的网关设备信息和群组号信息通知所 述移动管理网元对所述群组用户设备执行承载变更处理以及自身对所述群 组用户设备执行承载变更处理， 其中， 所述承载变更处理可以包括承载修 改流程， 或者， 可以包括承载去激活流程。 具体的流程可以包括：
流程 1 : 网关设备获知所述群组用户设备群组信息发生变化，通知所述 移动管理网元对所述群组用户设备执行承载修改以及自身对所述群组用户 设备执行承载修改；
E 201 , 网关设备（PGW )接收策略与计费规则功能实体（PCRF )发 送的 PCC消息 (例如 Policy and Charging Rules Response消息 )， 获知所述 群组用户设备 PCC规则发生变更； 或者网关设备 (例如分组数据网络网关） 接收移动管理网元发送的消息 （例如移动管理网元发送 Modify Bearer Command消息给服务网关， 服务网关再发送 Modify Bearer Command消息 给分组数据网络网关）， 获知所述群组用户设备信息发生变更（例如群组 QoS信息发生变更）； 或者网关设备（例如分组数据网络网关或网关 GRPS 支持节点）通过配置信息的变更（例如通过 0&M干涉）获知所述群组用户 设备群组信息发生变更。
E 202,分组数据网络网关发起针对所述群组用户设备的承载修改流程， 修改所述群组用户设备的上下文， 其中， 相同的所述移动管理网元信息和 所述服务网关信息和所述分组数据网络网关信息和所述群组号信息可以唯 一指示所述群组用户设备。
分组数据网络网关发送消息给服务网关， 所述消息可以是更新承载请 求（ Update Bearer Request ) 消息， 本实施例对所述消息的名称不 #丈限制。 所述消息包含所述移动管理网元信息和所述分组数据网络网关信息和所述 群组号信息， 或者， 可以包括所述移动管理网元信息和所述服务网关信息 和所述分组数据网络网关信息和所述群组号信息， 本实施对此不做限制。
其中， 所述分组数据网络网关发送所述消息给服务网关可以是为拥有 相同的所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息的所述群组用户设备发送一条所述消息给所述服 务网关， 而不是基于用户设备粒度发送多条现有修改承载请求消息。
E 203 , 服务网关根据接收步骤 E 204所述分组数据服务网关发送的所 述消息， 获知所述移动管理网元信息和所述服务网关信息和所述分组数据 网络网关信息和所述群组号信息， 具体可以通过如下实现：
若接收到的所述消息包括所述移动管理网元信息和所述分组数据网络 网关信息和所述群组号信息， 则所述服务网关可以从所述消息中获知所述 移动管理网元信息和所述分组数据网络网关信息和所述群组号信息， 此外， 所述服务网关可以根据获知的所述移动管理网元信息和所述分组数据网络 网关信息和所述群组号信息匹配在其上接入的所有用户设备上下文中的移 动管理网元信息和分组数据网络网关信息和群组号信息， 若匹配， 则服务 网关可以根据用户设备上下文信息获知自身信息 （服务网关信息）；
或者， 若接收到的所述消息所述移动管理网元信息和所述服务网关信 息和所述分组数据网络网关信息和所述群组号信息， 则服务网关可以从所 述消息中获知所述移动管理网元信息和所述服务网关信息和所述分组数据 网络网关信息和所述群组号信息。
所述服务网关可以给移动管理网元发送消息， 所述消息可以是更新承 载请求（ Update Bearer Request ) 消息， 本实施例对所述消息的名称不做限 制。 所述服务网关发送的所述消息可以包括所述分组数据网络网关信息和 所述服务网关信息和所述群组号信息， 或者， 可以包括所述移动管理网元 信息和所述服务网关信息和所述分组数据网络网关信息和所述群组号信 息， 本实施对此不做限制。
E 204, 移动管理网元根据接收步骤 E 203所述服务网关发送的所述消 息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 具体可以通过如下实现：
若接收到的所述消息只包括所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 则所述移动管理网元可以从所述消息中获知所 述服务网关信息和所述分组数据网络网关信息和所述群组号信息， 此外， 所述移动管理网元还可以根据获知的所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息匹配在其上接入的所有用户设备上下文中的 所述服务网关信息和所述分组数据网络网关信息和所述群组号信息， 若匹 配， 则移动管理网元可以根据用户设备上下文信息获知自身信息 （移动管 理网元信息）；
或者， 若接收到的所述消息包括所述移动管理网元信息和所述服务网 关信息和所述分组数据网络网关信息和所述群组号信息， 则所述移动管理 网元可以从所述消息中获知所述移动管理网元信息和所述服务网关信息和 所述分组数据网络网关信息和所述群组号信息。
移动管理网元根据获知的上述信息更新在其上接入的所述群组用户设 备的上下文信息。 具体方法可以是， 移动管理网元更新拥有 （保存）上述 移动管理网元根据接收步骤 E 203所述服务网关发送的所述消息获知的所 述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和 所述群组号信息或所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息的所述群组用户设备上下文。
移动管理网元可以发送消息给服务网关确定更新承载完成， 所述消息 可以是所述消息可以是更新承载响应 （ Update Bearer Response ) 消息，， 本 实施例对所述消息的名称不做限制。 所述消息包含所述移动管理网元信息 和所述分组数据网络网关信息和所述群组号信息， 或者， 可以包括所述移 动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息， 本实施对此不做限制
E 205 , 服务网关根据接收步骤 E 204所述移动管理网元发送的所述消 息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 具体可以通过如下实现 ：
若接收到的所述消息只包括所述移动管理网元信息和所述分组数据网 络网关信息和所述群组号信息， 服务网关可以从所述消息中获知移动管理 网元信息和所述分组数据网络网关信息和所述群组号信息， 此外， 服务网 关还可以根据获知的移动管理网元信息和所述分组数据网络网关信息和所 述群组号信息匹配在其上接入的所有用户设备上下文中的移动管理网元信 息和分组数据网络网关信息和群组号信息， 若匹配， 则服务网关可以根据 用户设备上下文信息获知自身信息 （服务网关信息）；
或者， 若接收到的所述消息包括所述移动管理网元信息和所述服务网 关信息和所述分组数据网络网关信息和所述群组号信息， 则服务网关可以 从所述消息中获知所述移动管理网元信息和所述服务网关信息和所述分组 数据网络网关信息和所述群组号信息。
服务网关根据获知的上述信息更新在其上接入的所述群组用户设备的 上下文信息。 具体方法可以是， 服务网关更新拥有 （保存）所述服务网关 根据接收步骤 E 204所述分组数据服务网关发送的所述消息获知的所述移 动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息或所述移动管理网元信息和所述分组数据网络网关信息和所述 群组号信息的所述群组用户设备上下文。
所述服务网关向分组数据网络网关发送消息确认承载更新完成， 所述 消息可以是更新 载响应 ( Update Bearer Response )消息， 本实施例对所述 消息的名称不做限制。 所述服务网关发送的所述消息可以包括所述服务网 关信息和所述移动管理网元信息和所述群组号信息， 或者， 可以包括所述 移动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和所 述群组号信息， 本实施对此不做限制。 E 206, 分组数据网络网关根据接收步骤 E 205所述服务网关发送的所 述消息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息， 具体可以通过如下实现 ：
若接收到的所述消息只包括所述移动管理网元信息和所述服务网关信 息和所述群组号信息， 则所述分组数据网络网关可以从所述消息中获知所 述移动管理网元信息和所述服务网关信息和所述群组号信息， 此外， 所述 分组数据网络网关还可以根据获知的所述移动管理网元信息和所述服务网 关信息和所述群组号信息匹配在其上接入的所有用户设备上下文中的移动 管理网元信息和服务网关和群组号信息， 若匹配， 则分组数据网络网关可 以根据用户设备上下文信息获知自身信息 （分组数据网络网关信息）；
或者， 若接收到的所述消息包括所述移动管理网元信息和所述服务网 关信息和所述分组数据网络网关信息和所述群组号信息， 则分组数据网络 网关可以从所述消息中获知所述移动管理网元信息和所述服务网关信息和 所述分组数据网络网关信息和所述群组号信息。
分组数据网络网关根据获知的上述信息更新在其上接入的所述群组用 户设备的上下文信息。 具体方法可以是， 分组数据网络网关更新拥有 （保 存）所述分组数据网络网关根据接收步骤 E 205所述服务网关发送的所述消 息获知的所述移动管理网元信息和所述服务网关信息和所述分组数据网络 网关信息和所述群组号信息或所述移动管理网元信息和所述服务网关信息 和所述群组号信息的所述群组用户设备上下文。
流程 2: 网关设备获知所述群组用户设备群组信息发生变化，通知所述 移动管理网元对所述群组用户设备执行承载去激活以及自身对所述群组用 户设备执行承载去激活；
E 301， 网关设备（PGW )接收策略与计费规则功能实体（PCRF )发 送的 PCC消息 (例如 Policy and Charging Rules Response消息 )， 例如获知 所述用户设备群组 PCC规则发生变更； 或者网关设备（例如分组数据网络 网关）接收移动管理网元发送的消息（例如移动管理网元发送 Modify Bearer Command消息给服务网关， 服务网关再发送 Modify Bearer Command消息 给分组数据网络网关）， 获知所述群组用户设备信息发生变更（例如原有签 约数据中的 APN在更新的签约数据中不可用）； 或者网关设备（例如分组 数据网络网关或网关 GRPS支持节点）通过配置信息的变更（例如通过 0&M 干涉）获知所述群组用户设备群组信息发生变更等。
E 302， 分组数据网络网关发起针对所述群组用户设备的承载去激活流 程， 去激活所述群组用户设备的上下文， 其中， 相同的所述移动管理网元 信息和所述服务网关信息和所述分组数据网络网关信息和所述群组号信息 可以唯一指示所述群组用户设备。 其中， 所述承载去激活流程还可以包括 分离流程。
分组数据网络网关发送消息给服务网关， 所述消息可以是删除承载请 求（Delete Bearer Request ) 消息， 本实施例对所述消息的名称不 #丈限制。 所述消息包含所述移动管理网元信息和所述分组数据网络网关信息和所述 群组号信息， 或者， 可以包括所述移动管理网元信息和所述服务网关信息 和所述分组数据网络网关信息和所述群组号信息， 本实施对此不做限制。
其中， 所述分组数据网络网关发送所述消息给服务网关可以是为拥有 相同的所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息的所述群组用户设备发送一条所述消息给所述服 务网关， 而不是基于用户设备粒度发送多条现有修改承载请求消息。
E 303， 服务网关根据接收步骤 E 304所述分组数据服务网关发送的所 述消息， 获知所述移动管理网元信息和所述服务网关信息和所述分组数据 网络网关信息和所述群组号信息， 具体可以参见步骤 E 203实现。
所述服务网关可以给移动管理网元发送消息， 所述消息可以是删除承 载请求（Delete Bearer Request ) 消息， 本实施例对所述消息的名称不做限 制。 所述服务网关发送的所述消息可以包括所述分组数据网络网关信息和 所述服务网关信息和所述群组号信息， 或者， 可以包括所述移动管理网元 信息和所述服务网关信息和所述分组数据网络网关信息和所述群组号信 息， 本实施对此不做限制。
E 304， 移动管理网元根据接收步骤 E 303所述服务网关发送的所述消 息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网络网 关信息和所述群组号信息， 具体可以参见步骤 E 204实现。
移动管理网元根据获知的上述信息去激活在其上接入的所述群组用户 设备的上下文信息。 具体方法可以是， 移动管理网元去激活拥有 （保存） 上述移动管理网元根据接收步骤 E 303所述服务网关发送的所述消息获知 的所述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信 息和所述群组号信息或所述服务网关信息和所述分组数据网络网关信息和 所述群组号信息的所述群组用户设备的上下文。
移动管理网元可以发送消息给服务网关确定去激活承载完成， 所述消 息可以是所述消息可以是删除承载响应（ Delete Bearer Response )消息， 本 实施例对所述消息的名称不做限制。 所述消息包含所述移动管理网元信息 和所述分组数据网络网关信息和所述群组号信息， 或者， 可以包括所述移 动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和所述 群组号信息， 本实施对此不做限制
E 305， 服务网关根据接收步骤 E 304所述移动管理网元发送的所述消 息获知所述移动管理网元信息和所述 务网关信息和所述分组数据网络网 关信息和所述群组号信息， 具体可以参见步骤 E 205实现 。
服务网关根据获知的上述信息去激活在其上接入的所述群组用户设备 的上下文信息。 具体方法可以是， 服务网关去激活拥有 （保存）所述服务 网关根据接收步骤 E 204所述分组数据服务网关发送的所述消息获知的所 述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和 所述群组号信息或所述移动管理网元信息和所述分组数据网络网关信息和 所述群组号信息的所述群组用户设备上下文。
所述服务网关向分组数据网络网关发送消息确认去激活承载完成， 所 述消息可以是删除承载响应（ Delete Bearer Response )消息， 本实施例对所 述消息的名称不做限制。 所述服务网关发送的所述消息可以包括所述服务 网关信息和所述移动管理网元信息和所述群组号信息， 或者， 可以包括所 述移动管理网元信息和所述服务网关信息和所述分组数据网络网关信息和 所述群组号信息， 本实施对此不做限制。
E 306, 分组数据网络网关根据接收步骤 E 305所述服务网关发送的所 述消息获知所述移动管理网元信息和所述服务网关信息和所述分组数据网 络网关信息和所述群组号信息， 具体可以参见步骤 E 206实现 。 分组数据网络网关根据获知的上述信息去激活在其上接入的所述群组 用户设备的上下文信息。 具体方法可以是， 分组数据网络网关去激活拥有 (保存）所述分组数据网络网关根据接收步骤 E 305所述服务网关发送的所 述消息获知的所述移动管理网元信息和所述服务网关信息和所述分组数据 网络网关信息和所述群组号信息或所述移动管理网元信息和所述服务网关 信息和所述群组号信息的所述群组用户设备上下文。
实施例 6
本发明实施例提供了一种基于 M2M应用的会话管理方法，流程参见图 6, 具体可以包括：
F 1， 网关设备获知群组用户设备的移动管理网元信息和群组号信息； 其中， 在此过程中， 移动管理网元也可以获知所述群组用户设备的网 关设备信息和群组号信息。 其中， 移动管理网元信息和群组号信息， 网关 设备信息和群组号信息的表示形式可以参见实施例 1步骤 A 101描述。 其 中， 移动管理网元获知群组用户设备的网关设备信息和群组号信息， 以及 网关设备获知群组用户设备的移动管理网元信息和群组号信息具体可参见 实施例 3步骤 C 1实现。
F 2 , 获知所述群组用户设备群组信息发生变更， 网关设备根据所述群 组用户设备的网关设备信息和所述群组号信息通知所述移动管理网元对所 述群组用户设备执行 PDP 上下文变更处理， 并对所述群组用户设备执行 PDP上下文变更处理；
网关设备根据所述群组用户设备的移动管理网元信息和群组号信息通 知所述移动管理网元对所述群组用户设备执行 PDP上下文变更处理以及自 身对所述群组用户设备执行 PDP上下文变更处理， 其中， 所述 PDP上下文 变更处理可以包括 PDP上下文修改流程， 或者， 可以包括 PDP上下文去激 活流程。 具体的流程可以包括：
流程 1 : 网关设备获知所述群组用户设备群组信息发生变化，通知所述 移动管理网元对所述群组用户设备执行 PDP上下文修改以及自身对所述群 组用户设备执行 PDP上下文修改；
F 201 , 网关设备（GGSN )接收策略与计费规则功能实体（PCRF )发 送的 PCC消息 (例如 Policy and Charging Rules Response消息 )， 获知所述 群组用户设备 PCC规则发生变更； 或者网关设备接收移动管理网元发送的 消息 （例如移动管理网元发送 Update Bearer Command消息给网关设备）， 获知所述群组用户设备信息发生变更（例如群组 QoS信息发生变更）； 或者 网关设备通过配置信息的变更（例如通过 0&M干涉）获知群组用户设备群 组信息发生变更。
F 202, 网络设备 (网关 GPRS支持节点 )发起针对所述群组用户设备 的 PDP上下文修改流程， 修改所述群组用户设备的 PDP上下文， 其中， 相 同的所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述群组号 信息可以唯一指示所述群组用户设备。
网关 GPRS支持节点发送消息给移动管理网元请求更新 PDP上下文， 所述消息可以是更新 PDP上下文请求（ Update PDP Context Request )消息， 本实施例对所述消息的名称不做限制。 所述消息可以包括所述网关 GPRS 支持节点信息和所述群组号信息， 或者， 可以包括所述移动管理网元信息 和所述网关 GPRS支持节点信息和所述群组号信息， 本实施对此不做限制。
其中， 所述网关 GPRS 支持节点发送所述消息给移动管理网元可以是 为拥有相同的所述移动管理网元信息和所述网关 GPRS 支持节点信息和所 述群组号信息的所述群组用户设备发送一条所述消息给所述网关 GPRS 支 持节点，而不是基于用户设备粒度发送多条现有更新 PDP上下文请求消息。
F 203 , 移动管理网元根据接收步骤 F 202所述网关 GPRS支持节点发 送的所述消息获知所述移动管理网元信息和所述网关 GPRS 支持节点信息 和所述群组号信息， 具体可以通过如下实现 ：
若接收到的所述消息只包括所述网关 GPRS 支持节点信息和所述群组 号信息， 则移动管理网元可以从所述消息中获知所述网关 GPRS 支持节点 信息和所述群组号信息。 此外， 所述移动管理网元可以根据获知的所述网 关 GPRS 支持节点信息和所述群组号信息匹配在其上接入的所有用户设备 上下文中的网关 GPRS 支持节点信息和群组号信息， 若匹配， 则移动管理 网元可以根据用户设备上下文信息获知自身信息 （移动管理网元信息）； 或者， 若接收到的所述消息包括所述移动管理网元信息和所述网关 GPRS支持节点信息和所述群组号信息，则所述移动管理网元可以从所述消 息中获知所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述群 组号信息。
移动管理网元根据获知的上述信息更新在其上接入的所述群组用户设 备的 PDP上下文信息。 具体方法可以是， 移动管理网元更新拥有 （保存） 上述移动管理网元根据接收步骤 F 202所述网关 GPRS支持节点发送的所述 消息获知的所述网关 GPRS 支持节点信息和所述群组号信息或所述移动管 理网元信息和所述网关 GPRS 支持节点信息和所述群组号信息的所述群组 用户设备 PDP上下文。
所述移动管理网元发送消息向网关 GPRS支持节点确认完成更新 PDP 上下文， 所述消息可以是更新 PDP 上下文响应 （Update PDP Context Response )消息， 本实施例对所述消息的名称不做限制。 所述移动管理网元 发送所述消息可以包含所述移动管理网元信息和所述群组号信息， 或者， 可以包括所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述群 组号信息， 本实施对此不做限制。
F 204, 网关 GPRS支持节点根据接收步骤 F 203所述移动管理网元发 送的所述消息获知所述移动管理网元信息和所述网关 GPRS 支持节点信息 和所述群组号信息， 具体可以通过如下实现 ：
若接收到的所述消息只包括所述移动管理网元信息和所述群组号信 息， 则网关 GPRS 支持节点可以从所述消息中获知所述移动管理网元信息 和所述群组号信息。 此外， 所述网关 GPRS 支持节点还可以根据所述移动 管理网元信息和所述群组号信息匹配在其上接入的所有用户设备上下文中 的移动管理网元设备信息和群组号信息， 若匹配， 则网关 GPRS 支持节点 可以根据用户设备上下文信息获知自身信息 （网关 GPRS支持节点信息）； 或者， 若接收到的所述消息包括所述移动管理网元信息和所述网关 GPRS支持节点信息和所述群组号信息，则网关 GPRS支持节点可以从所述 消息中获知所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述 群组号信息。
网关 GPRS 支持节点根据获知的上述信息更新在其上接入的所述群组 用户设备的 PDP上下文信息。 具体方法可以是， 网关 GPRS支持节点更新 拥有（保存 )上述网关 GPRS支持节点根据接收步骤 F 203所述移动管理网 元发送的所述消息获知的所述移动管理网元信息和所述群组号信息或所述 移动管理网元信息和所述网关 GPRS 支持节点信息和所述群组号信息的所 述群组用户设备 PDP上下文。
流程 2: 获知所述群组用户设备群组信息发生变化， 通知所述移动管理 网元对所述群组用户设备执行 PDP上下文去激活以及自身对所述群组用户 设备执行 PDP上下文去激活；
F 301 , 网关设备（GGSN )接收策略与计费规则功能实体（PCRF )发 送的 PCC消息 (例如 Policy and Charging Rules Response消息 )， 获知所述 群组用户设备 PCC规则发生变更； 或者网关设备接收移动管理网元发送的 消息 （例如移动管理网元发送 Update Bearer Command消息给网关设备）， 获知所述群组用户设备信息发生变更（例如群组 QoS信息发生变更）； 或者 网关设备通过配置信息的变更（例如通过 0&M干涉 )获知所述群组用户设 备群组信息发生变更。
F 302， 网络设备 (网关 GPRS支持节点 )发起针对所述群组用户设备 的 PDP上下文去激活流程，去激活所述群组用户设备的 PDP上下文，其中， 相同的所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述群组 号信息可以唯一指示所述群组用户设备。
网关 GPRS支持节点发送消息给移动管理网元请求去激活 PDP上下文， 所述消息可以是删除 PDP上下文请求（ Delete PDP Context Request ) 消息， 本实施例对所述消息的名称不做限制。 所述消息可以包括所述网关 GPRS 支持节点信息和所述群组号信息， 或者， 可以包括所述移动管理网元信息 和所述网关 GPRS支持节点信息和所述群组号信息， 本实施对此不做限制。
其中， 所述网关 GPRS 支持节点发送所述消息给移动管理网元可以是 为拥有相同的所述移动管理网元信息和所述网关 GPRS 支持节点信息和所 述群组号信息的所述群组用户设备发送一条所述消息给所述网关 GPRS 支 持节点，而不是基于用户设备粒度发送多条现有删除 PDP上下文请求消息。
F 303， 移动管理网元根据接收步骤 F 302所述网关 GPRS支持节点发 送的所述消息获知所述移动管理网元信息和所述网关 GPRS 支持节点信息 和所述群组号信息， 具体可以参见步骤 F 203实现 。
移动管理网元根据获知的上述信息去激活在其上接入的所述群组用户 设备的 PDP上下文信息。 具体方法可以是， 移动管理网元去激活拥有 （保 存）上述移动管理网元根据接收步骤 F 202所述网关 GPRS支持节点发送的 所述消息获知的所述网关 GPRS 支持节点信息和所述群组号信息或所述移 动管理网元信息和所述网关 GPRS 支持节点信息和所述群组号信息的所述 群组用户设备 PDP上下文。 所述移动管理网元发送消息向网关 GPRS 支持节点确认完成去激活 PDP上下文， 所述消息可以是删除 PDP上下文响应 （Delete PDP Context Response )消息， 本实施例对所述消息的名称不做限制。 所述移动管理网元 发送所述消息可以包含所述移动管理网元信息和所述群组号信息， 或者， 可以包括所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述群 组号信息， 本实施对此不做限制。
F 304， 网关 GPRS支持节点根据接收步骤 F 303所述移动管理网元发 送的所述消息获知所述移动管理网元信息和所述网关 GPRS 支持节点信息 和所述群组号信息， 具体可以参见步骤 F 204实现 ：
网关 GPRS 支持节点根据获知的上述信息去激活在其上接入的所述群 组用户设备的 PDP上下文信息。 具体方法可以是， 网关 GPRS支持节点去 激活拥有（保存）上述网关 GPRS支持节点根据接收步骤 F 203所述移动管 理网元发送的所述消息获知的所述移动管理网元信息和所述群组号信息或 所述移动管理网元信息和所述网关 GPRS 支持节点信息和所述群组号信息 的所述群组用户设备 PDP上下文。 相应地， 本发明实施例还提供了一种基于 M2M应用的会话管理系统， 该系统包括如图 7所示结构： 移动管理网元 701和网关设备 702， 其中： 移动管理网元 701，用于获知群组用户设备的网关设备信息和群组号信 息； 获知所述群组用户设备的群组信息发生变更； 根据所述群组用户设备 的网关设备信息和群组号信息通知所述网关设备 702对所述群组用户设备 执行承载变更处理； 对所述群组用户设备执行承载变更处理；
所述网关设备 702，用于获知群组用户设备的移动管理网元信息和群组 号信息； 获知所述群组用户设备的群组信息发生变更； 根据所述群组用户 设备的移动管理网元信息和群组号信息通知所述移动管理网元 701 对所述 群组用户设备执行承载变更处理； 对所述群组用户设备执行承载变更处理。
该实施例提供的一种基于 M2M应用的会话管理系统，可以用于执行本 发明实施例提供基于 M2M应用的会话管理方法。该系统进行会话管理的过 程， 可以参见本发明实施例所提供的基于 M2M应用的会话管理方法。
本实施例所提供的一种基于 M2M 应用的会话管理系统， 当系统中 M2M群组的共享签约数据发生更新时， 可以根据预先分配给群组用户设备 的网络设备资源分配标识信息以群组粒度对 M2M群组的相关信息进行统 一更新， 从而减少了网络侧信令的拥塞， 并相应减轻了网络负载。 另外， 本发明实施例还提供了一种移动管理网元， 该移动管理网元包 括如图 8所示结构： 第一获知单元 801、 第二获知单元 802、 第一通知单元 803和第一执行单元 804， 其中，
第一获知单元 801，用于获知群组用户设备的网关设备信息和群组号信 息；
第二获知单元 802， 用于获知所述群组用户设备的群组信息发生变化； 第一通知单元 803，用于根据所述群组用户设备的网关设备信息和群组 号信息通知所述网关设备对所述群组用户设备执行承载变更处理；
第一执行单元 804， 用于对所述群组用户设备执行承载变更处理。
该实施例提供的一种移动管理网元， 可以用于执行本发明实施例提供 基于 M2M应用的会话管理方法。该移动管理网元进行会话管理的过程， 可 以参见本发明实施例所提供的基于 M2M应用的会话管理方法。
本实施例所提供的一种移动管理网元，当系统中 M2M群组的共享签约 数据发生更新时， 可以根据预先分配给群组用户设备的网络设备资源分配 标识信息以群组粒度对 M2M群组的相关信息进行统一更新，从而减少了网 络侧信令的拥塞， 并相应减轻了网络负载。 最后， 本发明实施例还提供了一种网关设备， 该网关设备包括如图 9 所示结构： 第三获知单元 901、 第四获知单元 902、 第二通知单元 903和第 二执行单元 904， 其中，
第三获知单元 901，用于获知群组用户设备的移动管理网元信息和群组 号信息；
第四获知单元 902， 用于获知所述群组用户设备的群组信息发生变更； 第二通知单元 903，用于根据所述群组用户设备的移动管理网元信息和 群组号信息通知所述移动管理网元对所述群组用户设备执行承载变更处 理；
第二执行单元 904， 用于对所述群组用户设备执行承载变更处理。 该实施例提供的一种网关设备， 可以用于执行本发明实施例提供基于
M2M应用的会话管理方法。 该网关设备进行会话管理的过程， 可以参见本 发明实施例所提供的基于 M2M应用的会话管理方法。
本实施例所提供的一种网关设备，当系统中 M2M群组的共享签约数据 发生更新时， 可以根据群组用户设备的群组标识信息和预先分配给群组用 户设备的网络标识信息以群组粒度对 M2M群组的相关信息进行统一更新， 从而减少了网络侧信令的拥塞， 并相应减轻了网络负载。 本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步 骤可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机 可读取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述的存储介质包括： ROM ( Read-Only Memory, 只读存储记忆体）、 RAM ( Random Access Memory, 随机存储记忆体）、磁碟或者光盘等各种可 以存储程序代码的介质。 对所公开的实施例的上述说明， 使本领域专业技术人员能够实现或使 用本发明。 对这些实施例的多种修改对本领域的专业技术人员来说将是显 而易见的， 本文中所定义的一般原理可以在不脱离本发明的精神或范围的 情况下， 在其它实施例中实现。 因此， 本发明将不会被限制于本文所示的 这些实施例， 而是要符合与本文所公开的原理和新颖特点相一致的最宽的 范围。

Claims

权利要求
1、 一种基于 M2M应用的会话管理方法， 其特征在于， 包括： 获知群组用户设备的网关设备信息和群组号信息；
获知所述群组用户设备的群组信息发生变更；
根据所述群组用户设备的网关设备信息和群组号信息通知所述网关设 备对所述群组用户设备执行承载变更处理；
对所述群组用户设备执行承载变更处理。
2、 根据权利要求 1所述的方法， 其特征在于， 所述获知群组用户设备 的网关设备信息和群组号信息， 包括：
移动管理网元接收所述群组用户设备发送的接入请求消息；
移动管理网元发送创建的请求消息给网关设备， 所述消息包括所述群 组用户设备的移动管理网元信息和群组号信息；
移动管理网元接收网关设备返回的所述群组用户设备的网关设备信息 和群组号信息。
3、 根据权利要求 2所述的方法， 其特征在于， 所述移动管理网元发送 创建的请求消息给网关设备， 所述消息包括所述群组用户设备的移动管理 网元信息和群组号信息， 移动管理网元接收网关设备返回的所述群组用户 设备的网关设备信息和群组号信息， 包括：
移动管理网元发送创建的请求消息给服务网关， 所述移动管理网元发 送的创建的请求消息包括所述群组用户设备的移动管理网元信息和群组号 信息；
服务网关发送创建的请求消息给分组数据网络网关， 所述服务网关发 送的创建的请求消息包括所述群组用户设备的服务网关信息、 移动管理网 元信息和群组号信息；
分组数据网络网关发送创建的响应消息给服务网关， 所述分组数据网 络网关发送的创建的响应消息包括所述群组用户设备的分组数据网络网关 信息和群组号信息；
服务网关发送创建的响应消息给移动管理网元， 所述服务网关发送的 创建的响应消息包括所述群组用户设备的服务网关信息、 分组数据网络网 关信息和群组号信息。
4、 根据权利要求 1所述的方法， 其特征在于， 所述根据所述群组用户 设备的网关设备信息和群组号信息通知所述网关设备对所述群组用户设备 执行承载变更处理， 包括：
移动管理网元根据所述群组用户设备的服务网关信息和分组数据网络 网关信息和群组号信息发送变更的请求消息给所述服务网关， 所述移动管 理网元发送的变更的请求消息包括所述群组用户设备的移动管理网元信 息、 分组数据网关信息和群组号信息；
服务网关发送变更的请求消息给所述分组数据网络网关， 所述服务网 关发送的变更的请求消息包括所述群组用户设备的服务网关信息、 移动管 理网元信息和群组号信息；
分组数据网络网关根据所述服务网关发送的变更的请求消息获知所述 群组用户设备的移动管理网元信息、 服务网关信息、 分组数据网络网关信 息和群组号信息， 根据上述获知的信息对所述群组用户设备的上下文执行 载变更处理。
5、 根据权利要求 1所述的方法， 其特征在于， 所述对所述群组用户设 备执行承载变更处理， 包括：
分组数据网络网关发送变更的响应消息给所述服务网关， 所述分组数 据网络网关发送的变更的响应消息包括所述群组用户设备的分组数据网络 网关信息、 移动管理网元信息和群组号信息；
服务网关发送变更的响应消息给所述移动管理网元， 所述服务网关发 送的变更的响应消息包括所述群组用户设备的服务网关信息、 分组数据网 络网关信息和群组号信息；
移动管理网元根据所述服务网关发送的变更的响应消息获知所述群组 用户设备的移动管理网元信息、 服务网关信息、 分组数据网络网关信息和 群组号信息， 根据上述获知的信息对所述群组用户设备的上下文执行承载 变更处理。
6、 据权利要求 2所述的方法， 其特征在于， 所述移动管理网元发送创 建的请求消息给网关设备， 所述消息包括所述群组用户设备的移动管理网 元信息和群组号信息， 移动管理网元接收网关设备返回的所述群组用户设 备的网关设备信息和群组号信息， 包括： 移动管理网元发送创建的请求消息给网关 GPRS 支持节点， 所述移动 管理网元发送的创建的请求消息包括所述群组用户设备的移动管理网元信 息和群组号信息；
网关 GPRS 支持节点发送创建的响应消息给移动管理网元， 所述网关 GPRS支持节点发送的创建的响应消息包括所述群组用户设备的网关 GPRS 支持节点信息和群组号信息。
7、 根据权利要求 1所述的方法， 其特征在于， 所述根据所述群组用户 设备的网关设备信息和群组号信息通知所述网关设备对所述群组用户设备 执行承载变更处理， 包括：
移动管理网元根据所述群组用户设备的移动管理网元信息和群组号信 息发送变更的请求消息给所述网关 GPRS 支持节点， 所述移动管理网元发 送的变更的请求消息包括所述群组用户设备的移动管理网元信息和群组号 信息；
网关 GPRS 支持节点根据所述移动管理网元发送的变更的请求消息获 知所述群组用户设备的移动管理网元信息、 网关 GPRS 支持节点信息和群 组号信息， 根据上述获知的信息对所述群组用户设备的上下文执行 PDP上 下文变更处理。
8、 根据权利要求 1所述的方法， 其特征在于， 所述对所述群组用户设 备执行承载变更处理， 包括：
网关 GPRS 支持节点发送变更的响应消息给所述移动管理网元， 所述 网关 GPRS支持节点发送的变更的响应消息包括所述网关 GPRS支持节点 信息和所述群组号信息；
移动管理网元根据所述网关 GPRS 支持节点发送的所述消息获知所述 群组用户设备的移动管理网元信息、 网关 GPRS 支持节点信息和群组号信 息， 根据上述获知的信息对所述群组用户设备的上下文执行 PDP上下文变 更处理。
9、 一种基于 M2M应用的会话管理方法， 其特征在于， 包括： 获知群组用户设备的移动管理网元信息和群组号信息；
获知所述群组用户设备的群组信息发生变更； 根据所述群组用户设备的移动管理网元信息和群组号信息通知所述移 动管理网元对所述群组用户设备执行承载变更处理；
对所述群组用户设备执行承载变更处理。
10、 根据权利要求 9所述的方法， 其特征在于， 所述获知群组用户设 备的移动管理网元信息和群组号信息， 包括：
移动管理网元接收所述群组用户设备发送的接入请求消息；
网关设备接收移动管理网元发送的所述群组用户设备的移动管理网元 信息和群组号信息；
网关设备发送创建的响应消息给移动管理网元， 所述消息包括所述群 组用户设备的网关设备信息和群组号信息。
11、 根据权利要求 10所述的方法， 其特征在于， 所述网关设备接收移 动管理网元发送的所述群组用户设备的移动管理网元信息和群组号信息， 网关设备发送消息给移动管理网元， 所述消息包括所述群组用户设备的网 关设备信息和群组号信息， 包括：
移动管理网元发送创建的请求消息给服务网关， 所述移动管理网元发 送的创建的请求消息包括所述群组用户设备的移动管理网元信息和群组号 信息；
服务网关发送创建的请求消息给分组数据网络网关， 所述服务网关发 送的创建的请求消息包括所述群组用户设备的服务网关信息、 移动管理网 元信息和群组号信息；
分组数据网络网关发送创建的响应消息给服务网关， 所述分组数据网 络网关发送的创建的响应消息包括所述群组用户设备的分组数据网络网关 信息和群组号信息；
服务网关发送创建的响应消息给移动管理网元， 所述服务网关发送的 创建的响应消息包括所述群组用户设备的服务网关信息、 分组数据网络网 关信息和群组号信息。
12、 根据权利要求 9所述的方法， 其特征在于， 所述根据所述群组用 户设备的移动管理网元信息和群组号信息通知所述移动管理网元对所述群 组用户设备执行承载变更处理， 包括：
分组数据网络网关根据所述群组用户设备的服务网关信息和移动管理 网元信息和群组号信息发送变更的请求消息给所述服务网关， 所述分组数 据网络网关发送的变更的请求消息包括所述群组用户设备的移动管理网元 信息、 分组数据网关信息和群组号信息；
服务网关发送变更的请求消息给所述移动管理网元， 所述服务网关发 送的变更的请求消息包括所述群组用户设备的服务网关信息、 分组数据网 络网关信息和群组号信息；
移动管理网元根据所述服务网关发送的变更的请求消息获知所述群组 用户设备的移动管理网元信息、 服务网关信息、 分组数据网络网关信息和 群组号信息， 根据上述获知的信息对所述群组用户设备的上下文执行承载 变更处理。
13、 根据权利要求 9所述的方法， 其特征在于， 所述对所述群组用户 设备执行承载变更处理， 包括：
移动管理网元发送变更的响应消息给所述服务网关， 所述移动管理网 元发送的变更的响应消息包括所述群组用户设备的移动管理网元信息、 分 组数据网关信息和群组号信息；
服务网关发送变更的响应消息给所述分组数据网络网关， 所述服务网 关发送的变更的响应消息包括所述群组用户设备的服务网关信息、 移动管 理网元信息和群组号信息；
分组数据网络网关根据所述服务网关发送的变更的响应消息获知所述 群组用户设备的移动管理网元信息、 服务网关信息、 分组数据网络网关信 息和群组号信息， 根据上述获知的信息对所述群组用户设备的上下文执行 载变更处理。
14、 据权利要求 10所述的方法， 其特征在于， 所述网关设备接收移动 管理网元发送的所述群组用户设备的移动管理网元信息和群组号信息， 网 关设备发送创建的响应消息给移动管理网元， 所述消息包括所述群组用户 设备的网关设备信息和群组号信息， 包括：
移动管理网元发送创建的请求消息给网关 GPRS 支持节点， 所述移动 管理网元发送的创建的请求消息包括所述群组用户设备的移动管理网元信 息和群组号信息；
网关 GPRS 支持节点发送创建的响应消息给移动管理网元， 所述网关 GPRS支持节点发送的创建的响应消息包括所述群组用户设备的网关 GPRS 支持节点信息和群组号信息。
15、 根据权利要求 9所述的方法， 其特征在于， 所述根据所述群组用 户设备的移动管理网元信息和群组号信息通知所述移动管理网元对所述群 组用户设备执行承载变更处理， 包括：
网关 GPRS 支持节点根据所述群组用户设备的移动管理网元信息和群 组号信息发送变更的请求消息给所述移动管理网元， 所述网关 GPRS 支持 节点发送的变更的请求消息包括所述群组用户设备的网关 GPRS 支持节点 信息和群组号信息；
移动管理网元根据所述网关 GPRS 支持节点发送的变更的请求消息获 知所述群组用户设备的移动管理网元信息、 网关 GPRS 支持节点信息和群 组号信息， 根据上述获知的信息对所述群组用户设备的上下文执行 PDP上 下文变更处理。
16、 根据权利要求 9所述的方法， 其特征在于， 所述对所述群组用户 设备执行承载变更处理， 包括：
移动管理网元发送变更的响应消息给所述网关 GPRS 支持节点， 所述 移动管理网元发送的变更的响应消息包括所述群组用户设备的移动管理网 元信息和群组号信息；
网关 GPRS 支持节点根据所述移动管理网元发送的变更的响应消息获 知所述群组用户设备的移动管理网元信息、 网关 GPRS 支持节点信息和群 组号信息， 根据上述获知的信息对所述群组用户设备的上下文执行 PDP上 下文变更处理。
17、 一种移动管理网元， 其特征在于， 包括： 第一获知单元、 第二获 知单元、 第一通知单元和第一执行单元， 其中，
所述第一获知单元， 用于获知群组用户设备的网关设备信息和群组号 信息；
所述第二获知单元， 用于获知所述群组用户设备的群组信息发生变化； 所述第一通知单元， 用于根据所述群组用户设备的网关设备信息和群 组号信息通知所述网关设备对所述群组用户设备执行承载变更处理；
所述第一执行单元， 用于对所述群组用户设备执行承载变更处理。
18、 一种网关设备， 其特征在于， 包括： 第三获知单元、 第四获知单 元、 第二通知单元和第二执行单元， 其中，
所述第三获知单元， 用于获知群组用户设备的移动管理网元信息和群 组号信息；
所述第四获知单元， 用于获知所述群组用户设备的群组信息发生变更; 所述第二通知单元， 用于根据所述群组用户设备的移动管理网元信息 和群组号信息通知所述移动管理网元对所述群组用户设备执行承载变更处 理；
所述笫二执行单元， 用于对所述群组用户设备执行承载变更处理。
PCT/CN2011/070853 2010-02-11 2011-01-31 一种基于m2m应用的会话管理方法、系统和装置 WO2011098022A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2012552246A JP5603436B2 (ja) 2010-02-11 2011-01-31 Ｍ２ｍアプリケーションに基づいたセッション管理方法、システム及び装置
EP11741893.9A EP2528406B1 (en) 2010-02-11 2011-01-31 Method based on a machine to machine (m2m) application
US13/572,624 US8837326B2 (en) 2010-02-11 2012-08-11 Session management method and system based on M2M application, and apparatus
US14/481,341 US9271139B2 (en) 2010-02-11 2014-09-09 Session management method and system based on M2M application, and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010111544.7 2010-02-11
CN2010101115447A CN102158806B (zh) 2010-02-11 2010-02-11 一种基于m2m应用的会话管理方法、系统和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/572,624 Continuation US8837326B2 (en) 2010-02-11 2012-08-11 Session management method and system based on M2M application, and apparatus

Publications (1)

Publication Number Publication Date
WO2011098022A1 true WO2011098022A1 (zh) 2011-08-18

Family

ID=44367269

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070853 WO2011098022A1 (zh) 2010-02-11 2011-01-31 一种基于m2m应用的会话管理方法、系统和装置

Country Status (5)

Country Link
US (2) US8837326B2 (zh)
EP (1) EP2528406B1 (zh)
JP (1) JP5603436B2 (zh)
CN (1) CN102158806B (zh)
WO (1) WO2011098022A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013065297A1 (en) * 2011-11-02 2013-05-10 Panasonic Corporation Apparatus and methods for policy update of multiple communications devices
CN103152785A (zh) * 2011-12-06 2013-06-12 中国移动通信集团福建有限公司 一种物联网业务网关应答消息路由方法和系统

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9324173B2 (en) 2008-07-17 2016-04-26 International Business Machines Corporation System and method for enabling multiple-state avatars
US8957914B2 (en) * 2008-07-25 2015-02-17 International Business Machines Corporation Method for extending a virtual environment through registration
US10166470B2 (en) 2008-08-01 2019-01-01 International Business Machines Corporation Method for providing a virtual world layer
US9191942B2 (en) * 2011-03-09 2015-11-17 Lg Electronics Inc. Method and device for allocating group resources for M2M device in wireless communication system
RU2624106C2 (ru) * 2012-10-05 2017-06-30 Телефонактиеболагет Л М Эрикссон (Пабл) Сообщение относительно обслуживающей сети, часового пояса и uci
KR20140045215A (ko) * 2012-10-08 2014-04-16 삼성전자주식회사 그룹 기반 연결 설정 방법 및 장치
US9641347B2 (en) * 2012-10-08 2017-05-02 Lg Electronics Inc. Method and device for selecting packet data network gateway in wireless communication system
EP2915286A1 (en) * 2012-10-31 2015-09-09 Nokia Solutions and Networks Oy Management of a policy controlled group
US10834557B2 (en) * 2013-02-13 2020-11-10 Aeris Communications, Inc. Layered machine to machine (M2M) service methodology using class-based access point names (APNs) for the internet of things
US9215549B2 (en) 2013-02-13 2015-12-15 Aeris Communications, Inc. Method for delivering machine to machine (M2M) application control data over control plane in LTE/EPS utilizing standard bearer management procedures
US9596154B2 (en) * 2013-04-11 2017-03-14 Verizon Patent And Licensing Inc. Classifying client devices in a network
CN105247895B (zh) * 2013-05-29 2019-06-21 瑞典爱立信有限公司 用于管理在单播信道上发送的数据的发送的方法和配置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101472271A (zh) * 2008-03-13 2009-07-01 华为技术有限公司 对承载的处理方法及移动管理设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7761514B2 (en) 2003-11-26 2010-07-20 International Business Machines Corporation Method and apparatus for providing dynamic group management for distributed interactive applications
CN100372399C (zh) * 2004-11-19 2008-02-27 华为技术有限公司 一种实现集群业务的方法
CN101087446B (zh) 2006-06-09 2011-07-20 华为技术有限公司 一种群组会话的系统及方法
WO2009063434A1 (en) * 2007-11-16 2009-05-22 Nokia Siemens Networks Oy Mapping quality of service for intersystem handover
US8407769B2 (en) * 2008-02-22 2013-03-26 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for wireless device registration
JP2009246772A (ja) * 2008-03-31 2009-10-22 Panasonic Corp 移動管理装置及び無線通信基地局装置
EP2415288B1 (en) * 2009-04-03 2017-05-31 Panasonic Intellectual Property Corporation of America Mobile communication method, mobile communication system, and corresponding apparatus
CN102056140B (zh) * 2009-11-06 2013-08-07 中兴通讯股份有限公司 机器类通讯终端信息的获取方法和系统
CN102123477B (zh) * 2010-01-08 2015-06-10 中兴通讯股份有限公司 M2m核心网络的接入实现方法及装置
TW201215181A (en) * 2010-08-03 2012-04-01 Interdigital Patent Holdings Machine-to-machine (M2M) call flow security
US8787337B2 (en) * 2010-08-13 2014-07-22 Intel Corporation Techniques for managing mobility management signaling in a wireless network

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101472271A (zh) * 2008-03-13 2009-07-01 华为技术有限公司 对承载的处理方法及移动管理设备

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
See also references of EP2528406A4 *
SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS: "3GPP TR 23.888 V0.2.0: System Improvements for Machine-Type Communications; (Release 10)", 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 1 February 2010 (2010-02-01), XP050401845 *
SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS: "3GPP TS 22.368 Vl.0.0: Service requirements for machine-type communications; Stage 1 (Release 10)", 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 12 August 2009 (2009-08-12), pages 3 - 22, XP050361345 *
TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS: ""3GPP TR 22.868 V8.0.0: Study on Facilitating Machine to Machine Communication in 3GPP Systems (Release 8)", 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 23 March 2007 (2007-03-23), pages 4 - 14, XP050361381 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013065297A1 (en) * 2011-11-02 2013-05-10 Panasonic Corporation Apparatus and methods for policy update of multiple communications devices
CN103152785A (zh) * 2011-12-06 2013-06-12 中国移动通信集团福建有限公司 一种物联网业务网关应答消息路由方法和系统

Also Published As

Publication number Publication date
JP2013533647A (ja) 2013-08-22
US20120307798A1 (en) 2012-12-06
JP5603436B2 (ja) 2014-10-08
CN102158806A (zh) 2011-08-17
US20140376372A1 (en) 2014-12-25
EP2528406A1 (en) 2012-11-28
EP2528406B1 (en) 2018-11-28
CN102158806B (zh) 2012-08-08
EP2528406A4 (en) 2013-01-23
US9271139B2 (en) 2016-02-23
US8837326B2 (en) 2014-09-16

Similar Documents

Publication Publication Date Title
WO2011098022A1 (zh) 一种基于m2m应用的会话管理方法、系统和装置
CN111771394B (zh) 用于ue上下文和pdu会话上下文管理的系统和方法
JP2023062183A (ja) 時間依存ネットワーキングのための制御プレーンに基づく設定
CN110166580B (zh) 资源管理的方法、设备及系统
US10200908B2 (en) Methods, apparatus, a system, and a related computer program product for activation and deactivation of bearers
US20120063437A1 (en) Method for supporting pdn gw selection
WO2012051890A1 (zh) 终端接入限制的方法及系统
WO2012097731A1 (zh) 基于组的机器类型通信mtc设备的位置管理方法和设备
WO2009121251A1 (zh) 实现路由优化的方法、系统及装置
WO2011140884A1 (zh) Mtc组选择分组数据网网关的方法及移动性管理网元
JP7112831B2 (ja) 通信システム、および、通信方法
JP6957753B2 (ja) 課金方法、装置、及びシステム
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
WO2011050689A1 (zh) 机器类通讯终端的接入控制方法和系统
WO2014127688A1 (zh) 承载绑定方法及系统
WO2014166294A1 (zh) 临近业务服务器的选择方法及装置、用户注册方法及装置
WO2020034971A1 (zh) 分配ebi的方法和装置
WO2011110021A1 (zh) 一种策略控制方法、系统及策略控制器
WO2022052875A1 (zh) 终端跨区域通信方法、网元设备及存储介质
WO2018018469A1 (zh) 用户设备上下文管理方法、装置和设备
CN103379479B (zh) 一种确定用户标识和通知参数信息的方法、系统及设备
WO2019136695A1 (zh) 一种数据传输方法及装置、计算机存储介质
WO2020249101A1 (zh) 一种通信方法及装置
WO2013159605A1 (zh) 一种通信系统、装置和方法
JP2018137664A (ja) 通信システム、および、通信方法

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012552246

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 7264/CHENP/2012

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2011741893

Country of ref document: EP