WO2011060673A1 - 公用承载建立的方法、数据传输方法和核心网络侧设备 - Google Patents

公用承载建立的方法、数据传输方法和核心网络侧设备 Download PDF

Info

Publication number
WO2011060673A1
WO2011060673A1 PCT/CN2010/077744 CN2010077744W WO2011060673A1 WO 2011060673 A1 WO2011060673 A1 WO 2011060673A1 CN 2010077744 W CN2010077744 W CN 2010077744W WO 2011060673 A1 WO2011060673 A1 WO 2011060673A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
terminal
mtc
bearer
mtc group
Prior art date
Application number
PCT/CN2010/077744
Other languages
English (en)
French (fr)
Inventor
谢宝国
朱春晖
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011060673A1 publication Critical patent/WO2011060673A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation

Definitions

  • Public bearer establishment method for Public bearer establishment method, data transmission method and core network side device
  • the present invention relates to a bearer establishment technology in mobile communication, and in particular, to a public bearer establishment method, a data transmission method, and a core network side device. Background technique
  • M2M Machine to Machine
  • M2M service providers use existing wireless networks, such as General Packet Radio Service (GPRS) networks and Evolved Packet System (EPS) networks, to implement M2M services.
  • GPRS General Packet Radio Service
  • EPS Evolved Packet System
  • the 3rd Generation Partnership Project mainly uses GPRS network to realize data packet transmission.
  • 3GPP 3rd Generation Partnership Project
  • the performance requirements of the service layer for the bandwidth and delay of the transport layer are coming. The higher.
  • Evolved Radio Access Network Evolved Radio Access Network
  • E-RAN Evolved Radio Access Network
  • PDN Packet Data Network
  • EPC provides lower latency and allows more wireless access systems to access, including the following network elements:
  • the MME Mobility Management Entity
  • UE User Equipment
  • the security parameter, etc. allocates a temporary identifier to the user, and when the UE is camped on the tracking area or the network, is responsible for authenticating the user of the UE.
  • the Serving Gateway is a user plane entity that is responsible for user plane data routing processing and terminates downlink data of UEs in idle (ECM_IDLE) state. Manage and store the SAE bearer context of the UE, for example: IP bearer service parameters and network internal routing information.
  • the S-GW is the anchor point of the internal user plane of the 3GPP system. A user can only have one S-GW at a time.
  • the packet data network gateway (P-GW, PDN Gateway) is the gateway responsible for the UE accessing the PDN, assigns the user IP address, and is also the mobility anchor of the 3GPP and non-3GPP access systems.
  • the function of the P-GW also includes the policy implementation. , billing support. Users can access multiple P-GWs at the same time.
  • the Policy and Charging Enforcement Function (PCEF) is also located in the P-GW.
  • the Policy and Charging Rules Function (PCRF) is responsible for providing policy control and charging rules to the PCEF.
  • the home subscriber server (HSS) is responsible for permanently storing the subscriber data.
  • the content stored in the HSS includes the UE's International Mobile Subscriber Identification (IMSI) and the IP address of the P-GW.
  • MTC Server (Machine Type Communication Server) is a newly added network element for M2M applications. It is mainly responsible for information collection and data storage of machine type communication devices (MTC UE, Machine Type Communication Device). / Processing and other work, and the necessary management of the MTC UE.
  • the MTC UE is a terminal used by the M2M service. Similar to the UE, it also includes a Universal Integrated Circuit Card (UICC) and a Mobile Equipment (ME, Mobile Equipment). It is usually responsible for collecting information of several collectors and passing through the RAN node. Access the core network and interact with the MTC Server.
  • UICC Universal Integrated Circuit Card
  • ME Mobile Equipment
  • the MTC UE needs to transmit data information to the MTC Server or other MTC UEs through the SAE network.
  • the SAE network establishes a GPRS Tunneling Protocol (GTP) tunnel between the S-GW and the P-GW for this transmission, and the data information is reliably transmitted through the GTP tunnel.
  • GTP GPRS Tunneling Protocol
  • Step 201 The MTC UE initiates a network attach request to the eNodeB to access the SAE network, and carries information such as an IMSI, an MTC UE network access capability, and an instruction to allocate an IP.
  • Step 202 The eNodeB selects an MME for the MTC UE to serve, and forwards the attach request to the MME, and also carries important information such as the identifier of the MTC UE to the MME.
  • Step 203 The MME sends an authentication data request message (including an IMSI) to the HSS.
  • the HSS first determines the subscriber data corresponding to the IMSI. If no subscription is found or the IMSI is blacklisted, the HSS returns the authentication data to the MME. Responding to and carrying the appropriate error cause; if the subscriber data corresponding to the IMSI is found, the HSS returns an authentication data response message (including an authentication vector) to the MME.
  • the MME performs an authentication process to verify the legitimacy of the terminal IMSI and implements a security mode process. To enable a secure connection.
  • Step 204 The MME sends a location update request to the HSS of the home network, where the identifier of the MME and the identifier of the MTC UE are used to notify the HSS of the area currently accessed by the MTC UE.
  • Step 205 The HSS searches for the subscription user data of the MTC UE according to the identifier of the MTC UE, and sends the subscription user data to the MME.
  • the subscriber data mainly includes information such as the default access point name (APN, Access Point Name) and bandwidth.
  • the MME receives the subscriber data, checks whether the MTC UE is allowed to access the network, and returns a receiving user response to the HSS. If the MME finds that the MTC UE has roaming restrictions or access restrictions, the MME will prohibit the MTC UE from attaching and notify the HSS. .
  • Step 206 The HSS sends a confirmation location update response to the MME.
  • Step 207 The MME selects an S-GW for the MTC UE, and sends a request for establishing a default bearer.
  • the MME informs the S-GW of the necessary information: an identifier of the MTC UE, an identifier of the MME, an indication for assigning an IP address to the MTC UE, default bandwidth information, a P-GW address, and the like.
  • Step 208 The S-GW sends a request for establishing a default bearer to the P-GW.
  • the S-GW informs the P-GW of the necessary information, such as: an address of the S-GW, default bandwidth information, an indication for assigning an IP address to the MTC UE, and the like.
  • Step 209 If necessary, the P-GW requests the PCRF for the policy and charging rules and decision information configured for the MTC UE.
  • Step 210 The P-GW establishes a default bearer according to the policy and charging decision information returned by the PCRF, and returns a 7-load setup response to the S-GW.
  • Step 211 The S-GW sends a response to the default bearer establishment to the MME.
  • Step 212 The MME sends an attach accept response to the eNodeB, indicating that the request of the MTC UE to attach to the network has been accepted, and the response carries the address of the S-GW and the Tunnel Endpoint Identifier.
  • the radio bearer setup request carries the bearer network ID, the address of the P-GW, the IP address assigned to the MTC UE, the bandwidth information, and the like.
  • Step 214 The MTC UE sends a radio bearer setup response to the eNodeB, indicating that the radio bearer setup is complete.
  • Step 215 The eNodeB notifies the MME that the attach process is complete, and the TEID of the eNodeB and the address of the eNodeB are carried in the notification message.
  • Step 216 The MME sends an update bearer request to the S-GW, and notifies the TEID and address of the eNodeB served by the MTC UE, and establishes a GTP-based S1 access bearer between the eNodeB and the S-GW.
  • Step 217 The S-GW sends an update bearer response to the MME.
  • Step 218 If the P-GW is not specified by the HSS, the MME sends a location update request to the HSS, and notifies the HSS of the address information of the P-GW served by the MTC UE, and the HSS updates the information.
  • the M2M service is a networked application and service centered on intelligent interaction of machine terminals. It uses intelligent machine terminals to transmit information over the wireless network, providing customers with information solutions to meet customer information needs for monitoring, command and dispatch, data collection and measurement.
  • the communication object of M2M is machine-to-machine, which can be communication between people and machines, communication between machines and servers, and communication between different intelligent terminals.
  • Different application MTC UEs have different characteristics, such as elevators and other elevator devices have low mobility, only PS switched (Packet Switched only) attributes, while monitoring and alarm devices have low mobility, PS only, and Has attributes such as low data transfer and high availability. Therefore, different system optimizations are required for different application MTC UEs, which can effectively manage, monitor, and pay for the MTC UE. Fees, etc.
  • M2M terminals For M2M terminals, the service type is completely different from that of H2H terminals. According to statistics, more than 90% of M2M terminals are mainly low-mobility and low-data services, and their occupied bandwidth is negligible compared with H2H terminals. Since more than 90% of the M2M terminals are low-input attributes, the amount of data per day may not exceed several hundred bits.
  • the main purpose of the present invention is to provide a method for establishing a public bearer, a data transmission method, and a core network side device, so as to solve the problem that a large-scale M2M terminal consumes a large amount of network resources when accessing the network.
  • a method for establishing a public bearer provided by the present invention, the method comprising:
  • the core network side device establishes a group common bearer resource for a machine-to-machine communication (M2M) terminal in a machine type communication group (MTC Group);
  • M2M machine-to-machine communication
  • MTC Group machine type communication group
  • the core network side device allocates the group common bearer resource to the M2M terminal requesting access.
  • EPC evolved packet network
  • the group establishes a group public bearer resource for the M2M terminal in the MTC Group, which is specifically:
  • the core network side device reserves the group common bearer resource of the MTC group, and when the M2M terminal in the MTC group accesses the first time, the core network side device activates the reserved group public bearer resource;
  • the M2M terminal in the MTC Group accesses the EPC
  • the M2M terminal that requests the access is allocated a group common bearer resource, which is specifically:
  • the core network side device assigns the activated group of common bearer resources to the M2M terminal requesting access in the MTC Group.
  • the group is configured to establish a group public bearer resource for the M2M terminal in the MTC group, where: the core network side device does not reserve the group common bearer resource of the MTC group, and when the M2M terminal in the MTC Group accesses for the first time, The core network side device creates a group public bearer resource of the MTC Group;
  • the M2M terminal in the MTC Group accesses the EPC
  • the M2M terminal that requests the access is allocated a group common bearer resource, which is specifically:
  • the core network side device assigns the created group of common bearer resources to the M2M terminal requesting access in the MTC Group.
  • the M2M terminal that is requested to access the group to share the common bearer resource specifically: the core network side device according to the MTC Group identifier carried in the access request of the M2M terminal, or according to the subscription data of the M2M terminal that is requested to access Whether the MTC Group attribute is included, and whether the M2M terminal belongs to the MTC Group;
  • the invention also provides a data transmission method, the method comprising:
  • the core network side device allocates a common bearer resource for the M2M terminal requested to access in the MTC Group;
  • the core network side device creates and stores a correspondence between a wireless access network bearer channel and a group common bearer channel of each M2M terminal in the MTC group, and performs uplink and downlink transmission of data according to the corresponding relationship.
  • the corresponding relationship includes: an identifier of the M2M terminal, an IP address of the M2M terminal, an MTC Group identifier, a wireless port port identifier, and a public port port identifier.
  • the core network side device searches according to the identifier or IP address of the M2M terminal carried in the uplink data packet.
  • Corresponding public port tunnel port identifiers in the corresponding relationship, and forwarding the uplink data packet to a corresponding public bearer tunnel port;
  • the core network side device When receiving the downlink data packet sent to the M2M terminal in the MTC Group, the core network side device identifies the MTC Group identifier to which the downlink data packet belongs according to the IP address segment in the MTC Group, and forwards the downlink data packet to the corresponding office. And the core network side device searches for a corresponding radio bearer port identifier in the corresponding relationship according to the identifier or IP address of the M2M terminal carried in the downlink data packet, and the core network side device searches for the corresponding radio bearer port identifier in the corresponding relationship, and the The uplink packet is forwarded to the corresponding radio bearer tunnel port.
  • the present invention also provides a core network side device, including: a mobility management entity (MME), a serving gateway (S-GW), and a packet data network gateway (P-GW), where
  • MME mobility management entity
  • S-GW serving gateway
  • P-GW packet data network gateway
  • the S-GW and the P-GW are configured to establish a group public bearer resource for the M2M terminal in the MTC Group;
  • the MME is configured to receive an access request of the M2M terminal in the MTC Group, and request the S-GW and the P-GW to activate or create a group public bearer resource, and if the group public bearer resource is established,
  • the group public bearer resources established by the S-GW and the P-GW for the MTC Group are allocated to the M2M terminal requesting access.
  • the S-GW and the P-GW are further configured to reserve a group common bearer resource of the MTC group, and activate the reserved group public bearer resource when the M2M terminal in the MTC group accesses for the first time; And for assigning the activated group of common bearer resources to any M2M terminal requesting access within the MTC Group.
  • the S-GW and the P-GW are further configured to: when the M2M terminal in the MTC Group accesses for the first time, create a group public bearer resource of the MTC Group; For assigning the created group of common bearer resources to any M2M terminal requesting access within the MTC Group.
  • the MME is further configured to: according to the MTC Group identifier carried in the access request of the M2M terminal, or whether the MTC Group attribute is included in the subscription data of the M2M terminal that is requested to be accessed, and whether the M2M terminal belongs to the MTC Group;
  • the group common bearer resource is not activated or created for the M2M terminal.
  • the S-GW is further configured to: create and store a correspondence between a radio access network bearer channel and a group common bearer channel of each M2M terminal in the MTC group, where the correspondence includes: an identifier of the M2M terminal, and an M2M terminal IP address, MTC Group ID, radio bearer tunnel port ID, public port tunnel port ID.
  • the S-GW is further configured to: when receiving the uplink data packet sent by the M2M terminal in the MTC Group via the radio access network bearer channel, according to the M2M carried in the uplink data packet An identifier or an IP address of the terminal, searching for a corresponding public 7-port tunnel port identifier in the corresponding relationship, and forwarding the uplink data packet to a corresponding public bearer tunnel port.
  • the P-GW is further configured to, when receiving the downlink data packet sent to the M2M terminal in the MTC Group, identify the MTC Group identifier to which the downlink data packet belongs according to the IP address segment in the MTC Group, and configure the downlink data packet Forwarding to the public bearer tunnel port corresponding to the MTC Group identifier;
  • the S-GW is further configured to: when receiving the downlink data packet from the P-GW, search for a corresponding one of the corresponding relationships according to an identifier or an IP address of the M2M terminal carried in the downlink data packet
  • the radio bearers the tunnel port identifier and forwards the uplink data packet to the corresponding radio bearer tunnel port.
  • the method for establishing a public bearer, the data transmission method and the core network side device provided by the present invention classify a large number of M2M terminals with low data volume into multiple MTCs according to the principle of the same region or the same user at the time of signing.
  • the network establishes a common bearer shared by the devices in the group for each MTC Group, which saves network resources and reduces unnecessary overhead of frequently creating and unregistering bearers.
  • multiple devices share resources and effectively prevent EPS high bandwidth.
  • the inefficiency of the bearer ensures the reasonable allocation of network resources and the efficiency of the use of public bearers.
  • FIG. 1 is a schematic structural diagram of an EPS network system in the prior art
  • FIG. 2 is a flow chart of attaching an MTC UE to an EPS network in the prior art
  • FIG. 3 is a flow chart of a method for establishing a public bearer according to the present invention.
  • FIG. 4 is a flowchart of attaching an MTC UE to an EPS network according to Embodiment 1 of the present invention
  • FIG. 5 is a flowchart of attaching an MTC UE to an EPS network according to Embodiment 2 of the present invention
  • FIG. 6 is an MTC UE attached according to Embodiment 3 of the present invention
  • FIG. 7 is a flowchart of attaching an MTC UE to an EPS network according to Embodiment 4 of the present invention.
  • a method for establishing a public bearer based on MTC Group optimization mainly includes the following steps:
  • Step 301 The core network side device establishes a group public bearer resource for the M2M terminal in the MTC Group.
  • Step 302 When the M2M terminal in the MTC Group accesses the EPC, the core network device allocates the group common bearer resource for the M2M terminal requesting access.
  • the first mode Pre-press the MTC Group to reserve the group common bearer resources in the relevant network elements of the network.
  • the M2M terminal in the MTC Group accesses the network for the first time, activate the group public bearer resources reserved by the network;
  • the activated public bearer resource is assigned to the M2M terminal in the MTC Group in the attaching process, so that the device in the MTC Group can share the shared bearer after accessing the device.
  • Resources to implement M2M services For example: There are four M2M terminals A, B, C, and D in an MTC Group.
  • the M2M terminal that accesses the network for the first time in the MTC Group is the terminal A
  • the active network is the MTC Group.
  • the reserved group public bearer resources, and the activated public bearer resources are allocated to the terminal A; when the terminal B accesses the network, the activated public bearer resources are directly assigned to the terminal B in the attaching process of the terminal B.
  • the terminal C or D accesses the network, the public bearer resource that has been activated is directly assigned to the terminal C or D in the attaching process of the terminal C or D.
  • the second mode the group public bearer resources in the MTC Group are reserved in the network element of the network in advance.
  • the core network side The device creates a group common bearer resource for the MTC group; when a subsequent M2M terminal accesses the network in the MTC Group, the established group public bearer resource is assigned to the M2M terminal in the MTC Group in the attaching process, After the devices in the MTC Group are connected, the group common bearer resources can be shared to implement the M2M service. For example, there are four M2M terminals A, B, C, and D in an MTC Group.
  • the core network side device is the The MTC group creates a group common bearer resource, and allocates the created group common bearer resource to the terminal A.
  • the established public bearer resource is directly assigned to the terminal in the attaching process of the terminal B.
  • the terminal C or D accesses the network, the established public bearer resource is directly assigned to the terminal C or D in the attaching process of the terminal C or D.
  • the core network side device receives the access request of the M2M terminal, according to the MTC Group identifier carried in the access request of the M2M terminal, or according to the subscription data of the M2M terminal that is requested to access, whether the MTC Group attribute is included, To identify whether the M2M terminal belongs to the MTC Group;
  • the above two methods are to establish a common bearer channel for the MTC Group on the core network side of the EPC, but on the wireless network side of the radio access technology (RAT, Radio Access Technology), it is also required for each M2M terminal.
  • the radio bearer channel of the terminal to the eNodeB and the access bearer channel of the eNodeB to the S-GW are separately established, and the radio bearer channel and the access bearer channel may be collectively referred to as a radio access network bearer channel. Therefore, the S-GW needs to create and save the radio access network bearer channel and the group common bearer channel of each M2M terminal in the MTC Group.
  • the correspondence may include information such as an identifier (ID) of the M2M terminal, an IP address of the M2M terminal, an MTC Group identifier, a radio bearer tunnel port identifier, and a public bearer tunnel port identifier.
  • ID an identifier
  • the S-GW uses the ID or IP address of the M2M terminal in the data packet as the uplink data packet according to the corresponding relationship.
  • the corresponding network side common bearer channel is found, and the uplink data packet is forwarded to the public bearer tunnel port.
  • the P-GW can identify that the downlink data packet belongs to the device in the MTC Group through the IP address segment in the MTC Group, and then forward the downlink data packet to the corresponding MTC.
  • the public bearer tunnel port of the group when the downlink data packet is sent to the S-GW, the S-GW will downlink according to the ID of the M2M terminal or the IP address of the M2M terminal, and the corresponding relationship between the radio access network bearer channel of the device and the common bearer channel. The packet is forwarded to the corresponding radio bearer tunnel port.
  • the network is a contracted MTC Group that reserves a group common bearer resource in the relevant network element.
  • the network activates the group of the MTC Group.
  • the public bearer resource completes the establishment of the shared bearer shared within the group.
  • the correspondence between the radio access network channel of each M2M terminal in the MTC Group and the common bearer channel in the core network side group needs to be created and saved.
  • Step 401 The M2M terminal (that is, the MTC UE shown in FIG. 4) signs the MTC Group ID (ie, the MTC Group ID) when signing the contract, and the MTC Group may sign according to the same industry user or the same area.
  • MTC Group ID ie, the MTC Group ID
  • the MTC Group may sign according to the same industry user or the same area.
  • a plurality of MTC Groups are contracted in the EPC network.
  • the EPC network reserves the common bearer resources, such as tunnel traffic, for the MTC Groups on the S-GW and the P-GW according to the configuration tools such as the network management configuration server. Template (TFT, Tunnel Flow Template) port, S-GW address and TEID, P-GW address and TEID, group QoS rules and other resources.
  • Step 402 When the MTC UE belonging to the MTC Group accesses the EPS network for the first time, initiate a network attach request to the eNodeB, where the request carries the information such as the IMSI, the MTC Group ID, the MTC UE network access capability, and the request for IP allocation. .
  • the IP address of the MTC UE can be statically configured, or the dynamically assigned IP address can be obtained through the Domain Name System (DNS) server.
  • DNS Domain Name System
  • the MTC Group ID is used to indicate that the MTC UE belongs to the MTC Group identified by this ID.
  • Step 403 The eNodeB selects an MME to serve the MTC UE, and forwards the attach request to the MME, and also carries important information such as the MTC UE identifier and the MTC Group ID to the MME.
  • Step 404 The MME performs an authentication process, and then sends a location update request to the HSS of the home network, where the MME carries the identifier of the MME and the identifier of the MTC UE.
  • the HSS searches for the subscriber data of the MTC UE according to the identifier of the MTC UE and sends the data to the MME.
  • the subscriber data mainly includes the default APN, the bandwidth size, and the like.
  • the MTC Group ID is also included to indicate which group the MTC UE belongs to.
  • Step 405 The MME receives the subscription user data, and checks whether the MTC UE is allowed to access the network. If the MME finds that the MTC UE has roaming restrictions or access restrictions, the MME will prohibit the MTC UE from attaching and notify the HSS.
  • the MME searches for the group public bearer corresponding to the MTC Group ID according to the MTC Group ID carried in the attached message by the MTC UE or the MTC Group ID in the subscription user data. If the terminal in the MTC Group accesses for the first time and the group public bearer is not activated, the MME sends a group public bearer activation request of the MTC Group to the S-GW, where the MTC Group ID and the assigned group public bearer ID (MTC Group LID) are carried. .
  • Step 406 After receiving the group public bearer activation request of the MTC Group, if the S-GW finds that the group public bearer of the MTC Group has been activated, the S-GW directly jumps to step 407; If the group public bearer of the group is not activated, the TEID port of the S-GW reserved for the MTC Group ID is activated, the TEID port corresponding to the P-GW side is configured, and the active group request is sent to the P-GW, where the MTC is carried. Group ID, MTC Group LID and other information.
  • the P-GW activates the TFT port and the TEID port reserved for the MTC Group ID, and configures the TEID port corresponding to the S-GW side, allocates the group QoS, and notifies the S-GW that the reserved group common bearer resource is activated.
  • the public bearer channel reserved for the MTC Group ID on the core network side is activated.
  • Step 407 After the public bearer is activated, the S-GW sends an active public bearer response to the MME to the MME, where the information carries the information such as the MTC Group LID, the address of the P-GW, the address of the S-GW, and the S-GW TEID, indicating the group public bearer. activated.
  • Step 408 The MME associates the MTC Group ID, the MTC Group LID, and the address of the S-GW.
  • the message carries the MTC Group LID, the address of the P-GW, the address of the S-GW, and the S -GW TEID and other information.
  • Step 409 The eNodeB sends a radio bearer setup request to the MTC UE, and the MTC UE saves related information such as QoS established by the bearer, and opens the corresponding TFT port.
  • the request carries: a radio bearer ID, a P-GW address, bandwidth information, and the like.
  • the MTC UE sends a radio bearer setup complete message to the eNodeB, and the MTC UE and the eNodeB have established a radio bearer channel and use the radio bearer ID for identification.
  • Step 410 The eNodeB sends an attach complete message to the MME, where the eNodeB TEID, the eNodeB address, and the like are carried, and the MME attach procedure is notified.
  • Step 411 The MME sends an update bearer request to the S-GW, where the identifier of the MTC UE and the MTC Group LID are carried, and the information of the TEID of the eNodeB and the address of the eNodeB that the S-GW serves for the MTC UE are notified.
  • Step 412 The S-GW identifies, according to the MTC Group LID, that the uplink and downlink addresses and ports of the public bearer of the group are updated, and saves the identifier of the MTC UE/the IP address of the MTC UE, and the MTC Group. Correspondence between the LID, the eNodeB TEID, and the S-GW TEID.
  • the MTC UE sends or receives the uplink and downlink data packets, it can identify the MTC UE or the IP address of the MTC UE according to the identifier of the MTC UE, and forward the data packet to the corresponding according to the corresponding relationship. Port.
  • Step 413 The S-GW sends an update bearer response to the MME, indicating that the GTP tunnel (S1 user plane access bearer) of the eNodeB to the S-GW has been successfully established, and the MTC UE can send or receive the context data packet through the S-GW.
  • GTP tunnel S1 user plane access bearer
  • the network has activated the group common bearer resources reserved for the MTC Group, and establishes a group common bearer of the MTC Group.
  • the network directly The established group public bearer is assigned to the M2M terminal that initiated the attach request.
  • the correspondence between the radio access network bearer channel of each M2M terminal accessed in the MTC Group and the common bearer channel in the core network side group needs to be created and saved.
  • Step 501 When the M2M terminal in the MTC Group accesses for the first time, the MME requests the S-GW to activate the public bearer, and the S-GW/P-GW activates the TFT port, the S-GW address, the TEID, and the P-GW address for the MTC Group. For the TEID, the group QoS rule, and other resources, the public bearer resource reserved by the MTC Group is activated.
  • the group public bearer identified by the MTC Group LID between the S-GW and the P-GW can be shared by the devices in the MTC Group.
  • Step 502 When the other MTC UEs belonging to the MTC group access the EPS network, initiate a network attach request to the eNodeB, where the information such as the IMSI, the MTC Group ID, and the network access capability of the MTC UE are carried.
  • the IP address of the MTC UE can be statically configured, or the dynamically assigned IP address can be obtained through the DNS server.
  • the MTC Group ID indicates that the MTC UE belongs to the MTC Group identified by the ID.
  • Step 503 The eNodeB forwards the attach request to the MME, and also carries important information such as the identifier of the MTC UE and the MTC Group ID to the MME.
  • Step 504 The MME performs an authentication process, and then sends a location update request to the HSS of the home network, where the identifier of the MME and the identifier of the MTC UE are carried.
  • the HSS searches for the subscriber data of the MTC UE according to the identifier of the MTC UE and sends the data to the MME.
  • the subscriber data mainly includes information such as APN, bandwidth, and the like, and also includes the MTC Group ID.
  • Step 505 The MME receives the user subscription data, and checks whether the MTC UE is allowed to access the network. If the MME finds that the MTC UE has roaming restrictions or access restrictions, the MME prohibits the MTC UE from attaching and notifies the HSS.
  • the MME searches for the group public bearer corresponding to the MTC Group ID according to the MTC Group ID carried in the attached message by the MTC UE or according to the MTC Group ID in the subscription user data. If the group public bearer is activated, the MME finds the MTC Group LID, the address of the P-GW, the address of the S-GW, and the S-GW TEID from the associated data of the MTC Group, and sends an attach accept message to the eNodeB, indicating that the MTC UE is attached. A request to the network has been accepted.
  • the group common bearer of the MTC Group needs to be created when the M2M terminal in the MTC Group accesses for the first time.
  • the correspondence between the radio access network bearer channel of each M2M terminal accessed in the MTC Group and the group public channel on the core network side needs to be created and saved.
  • Step 601 When the MTC UE belonging to the MTC Group accesses the EPS network for the first time, it initiates a network attach request to the eNodeB, and carries information such as an IMSI, an MTC Group ID, a network access capability of the MTC UE, and an instruction to allocate an IP.
  • information such as an IMSI, an MTC Group ID, a network access capability of the MTC UE, and an instruction to allocate an IP.
  • IP address of the MTC UE can be statically configured, or the dynamically assigned IP address can be obtained through the DNS server.
  • Step 602 The eNodeB selects an MME for the MTC UE to serve, and attaches The request is forwarded to the MME, and important information such as the identifier of the MTC UE and the MTC Group ID is also carried to the MME.
  • Step 603 The MME performs an authentication process, and then sends a location update request to the HSS of the home network, where the MME carries the identifier of the MME and the identifier of the MTC UE.
  • the HSS finds the subscriber data of the MTC UE according to the identifier of the MTC UE and sends it to the MME.
  • the subscriber data mainly includes information such as APN, bandwidth, and the MTC Group ID.
  • the MME receives the user subscription data and checks whether the MTC UE is allowed to access the network. If the MME finds that the MTC UE has roaming restrictions or access restrictions, the MME will prohibit the MTC UE from attaching and notify the HSS.
  • Step 604 If the MTC UE has no access restriction, the MME searches for the group public bearer corresponding to the MTC Group ID according to the MTC Group ID carried by the MTC UE in the attach message or according to the MTC Group ID in the subscription data. If the terminal is first accessed in the MTC Group and the group public bearer is not created, the MME sends a create group common bearer request to the S-GW, where the request carries the MTC UE identifier, the MTC Group ID, the MTC Group LID, the P-GW address, and the like. information.
  • Step 605 After receiving the group public bearer creation request, if the group public bearer is found to be created, the S-GW directly jumps to step 608 to send a create group public bearer response message to the MME; if the group public bearer is not created, then S - GW creates a new entry for the group public bearer and then sends a group public bearer request to the P-GW to create the MTC Group. In the request, the S-GW informs the P-GW of the necessary information: the MTC Group LID, the address and TEID of the S-GW, and the default bandwidth information.
  • Step 606 If necessary, the P-GW requests the PCRF to configure the QoS policy and the charging rule for the MTC Group, and the PCRF sends the PCC rule corresponding to the MTC Group to the P-GW.
  • Step 607 The P-GW establishes a group public bearer according to the policy and charging decision information returned by the PCRF, and returns a group public bearer setup response to the S-GW, where the response carries With the MTC Group public bearer ID, P-GW address and TEID information.
  • Step 608 The S-GW updates and saves the MTC Group LID corresponding to the MTC Group identifier, the address of the P-GW, and the TEID, and the GTP public tunnel of the S-GW to the P-GW is successfully established.
  • the S-GW sends a create group public bearer response to the MME to the MME, where the response carries the information such as the MTC Group LID, the address of the P-GW, the address of the S-GW, and the S-GW TEID, indicating the public bearer. Created.
  • the network has created a group common bearer resource for the MTC Group, and established a group common bearer of the MTC Group; when other M2M terminals of the MTC Group access the network, the network directly will be established.
  • the group public bearer is assigned to the M2M terminal that initiated the attach request.
  • the correspondence between the radio access network bearer channel of each M2M terminal in the MTC Group and the common bearer channel in the group on the core network side needs to be created and saved.
  • Step 701 When the M2M terminal in the MTC Group accesses for the first time, the MME requests to create a group public bearer of the MTC Group. After receiving the group public bearer creation request, the S-GW/P-GW allocates a TFT port to the MTC Group, and the S- The GW address and the resources such as the TEID, the P-GW address, and the TEID successfully create a group public bearer identified by the MTC Group LID between the S-GW and the P-GW.
  • Step 702 When the other MTC UEs belonging to the MTC Group access the EPS network, initiate a network attach request to the eNodeB, where the information such as the IMSI, the MTC Group ID, and the network access capability of the MTC UE are carried.
  • IP address of the MTC UE can be statically configured, or the dynamically assigned IP address can be obtained through the DNS server.
  • Step 703 The eNodeB forwards the attach request to the MME, and simultaneously marks the MTC UE. Important information such as knowledge and MTC Group ID is also carried to the MME.
  • Step 704 The MME performs an authentication process, and then sends a location update request to the HSS of the home network, where the MME carries the identifier of the MME and the identifier of the MTC UE.
  • the HSS finds the subscriber data of the MTC UE according to the identifier of the MTC UE and sends it to the MME.
  • the subscriber data mainly includes information such as APN, bandwidth, and the MTC Group ID.
  • Step 705 The MME receives the user subscription data, and checks whether the MTC UE is allowed to access the network. If the MME finds that the MTC UE has roaming restrictions or access restrictions, the MME will prohibit the MTC UE from attaching and notify the HSS.
  • the MME searches for the group public bearer corresponding to the MTC Group ID according to the MTC Group ID carried in the attached message by the MTC UE or the MTC Group ID in the subscription user data. If the group public bearer has been created, the MME finds the MTC Group LID, the address of the P-GW, the address of the S-GW, and the S-GW TEID from the associated data of the MTC Group, and sends an attach accept message to the eNodeB, indicating that the MTC UE is attached. A request to the network has been accepted.
  • Step 706 The eNodeB sends a radio bearer setup request to the MTC UE, and the MTC UE saves related information such as QoS established by the bearer, and opens the corresponding TFT port.
  • the radio bearer setup request carries: a radio bearer ID, a P-GW address, bandwidth information, and the like.
  • the MTC UE sends a radio bearer setup complete message to the eNodeB, and the MTC UE and the eNodeB have established a radio bearer channel, and the radio bearer ID is used for identification.
  • Step 707 The eNodeB sends an attach complete message to the MME, where the message carries information such as the eNodeB TEID and the eNodeB address, and notifies the MME that the attach process is complete.
  • Step 708 The MME sends an update bearer request to the S-GW, which carries the identifier of the MTC UE, the MTC Group LID, and notifies the S-GW of the TEID of the eNodeB served by the MTC UE, the address of the eNodeB, and the like.
  • Step 709 The S-GW identifies, according to the MTC Group LID, that the public bearer of the update group is up and down.
  • the row address and the port are used to store the mapping between the MTC UE's identity/the MTC UE's IP address, the MTC Group LID, the eNodeB TEID, and the S-GW TEID.
  • the MTC UE sends or receives the uplink and downlink data packets, the MTC UE can be used.
  • the identifier or the IP address of the MTC UE is identified, and the data packet is forwarded to the corresponding port according to the above correspondence.
  • Step 710 The S-GW sends an update bearer response to the MME, indicating that the GTP tunnel (S1 user plane access bearer) of the eNodeB to the S-GW has been successfully established, and the MTC UE can send or receive the context data packet through the S-GW.
  • GTP tunnel S1 user plane access bearer
  • the method for implementing the above-mentioned common bearer establishment in the present invention, and the core network side device of the data transmission method are composed of: an MME, an S-GW, and a P-GW, where the S-GW and the P-GW are used for the MTC Group.
  • the M2M terminal establishes a group common bearer resource; the MME is configured to receive an access request of the M2M terminal in the MTC Group, and request activation or create a group public bearer from the S-GW and the P-GW, if the group public bearer is established,
  • the group public bearer resources established by the S-GW and the P-GW for the MTC Group are allocated to the M2M terminal requesting access.
  • the S-GW and the P-GW are further configured to reserve a group common bearer resource of the MTC Group, and activate the reserved group common bearer resource when the M2M terminal in the MTC Group accesses for the first time;
  • the activated group common bearer resources are assigned to any M2M terminal within the MTC Group requesting access.
  • the S-GW and the P-GW do not reserve the group common bearer resource of the MTC Group, and when the M2M terminal in the MTC Group accesses for the first time, the group public bearer resource of the MTC Group is created; and is also used to share the created group.
  • the bearer resources are assigned to any M2M terminal within the MTC Group requesting access.
  • the MME is further configured to: identify, according to the MTC Group identifier carried in the access request of the M2M terminal, whether the M2M terminal belongs to the MTC Group according to whether the MTC Group attribute of the M2M terminal that is requested to be accessed includes the MTC Group attribute; If yes, it identifies whether the corresponding group public bearer resource is activated or created according to the MTC Group identifier.
  • the group public bearer resource that is activated or created is directly assigned to the M2M terminal; And creating, requesting the S-GW and the P-GW to activate or create a group public bearer resource corresponding to the MTC Group identifier, and assigning to the M2M terminal; if not, the group public bearer resource need not be activated or created for the M2M terminal.
  • the S-GW is further configured to: create and store a correspondence between a radio access network bearer channel and a group common bearer channel of each M2M terminal in the MTC group, where the correspondence includes: an identifier of the M2M terminal, and an M2M terminal IP address, MTC Group ID, radio bearer tunnel port ID, public tunnel port ID.
  • the S-GW When receiving the uplink data packet sent by the M2M terminal in the MTC Group via the radio access network bearer channel, the S-GW searches for the corresponding common bearer tunnel port in the corresponding relationship according to the identifier or IP address of the M2M terminal carried in the uplink data packet. Identifies and forwards the upstream packet to the corresponding public bearer tunnel port.
  • the P-GW When receiving the downlink data packet sent to the M2M terminal in the MTC Group, the P-GW identifies the MTC Group identifier to which the downlink data packet belongs according to the IP address segment in the MTC Group, and forwards the downlink data packet to the public corresponding to the MTC Group identifier.
  • the S-GW searches for the corresponding radio bearer port identifier in the corresponding relationship according to the identifier or IP address of the M2M terminal carried in the downlink data packet. And forward the upstream packet to the corresponding radio bearer tunnel port.
  • the present invention divides a large number of M2M terminals with a small amount of data into multiple MTC Groups according to the same region or the same user at the time of signing, and the network establishes a common bearer shared by the devices in the group for each MTC Group. This not only saves network resources, but also reduces the unnecessary overhead of frequently creating and unregistering bearers. Moreover, multiple devices share resources, which effectively prevents the inefficiency of EPS high-bandwidth bearers and ensures the rational allocation of network resources and public bearers. Use efficiency.

Landscapes

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

Abstract

本发明公开了一种公用承载建立的方法，包括：核心网络侧设备为机器类通信组（MTCGroup）内的机器到机器间的通信（M2M）终端建立组公用承载资源；在MTCGroup内的M2M终端接入演进的分组网（EPC）时，核心网络侧设备为请求接入的M2M终端分配组公用承载资源。本发明还公开了一种数据传输方法，包括：核心网络侧设备为MTCGroup内请求接入的M2M终端分配公用承载资源；核心网络侧设备创建并存储MTCGroup内各M2M终端的无线接入网络承载通道与组公用承载通道的对应关系，并依据该对应关系执行数据的上下行传输。通过本发明，解决了规模巨大的M2M终端接入到网络时，会占用大量网络资源的问题。

Description

公用承载建立的方法、 数据传输方法和核心网络侧设备 技术领域
本发明涉及移动通信中的承载建立技术， 尤其涉及一种公用承载建立 的方法、 数据传输方法和核心网络侧设备。 背景技术
近年来， 机器到机器间的通信（M2M, Machine to Machine )业务逐渐 开始得到应用， 如物流***、 远程抄表、 智能家居等应用。 M2M服务商使 用现有的无线网络， 如通用分组无线业务（ GPRS , General Packet Radio service ) 网络、 演进分组***（EPS , Evolved Packet System ) 网络等， 开 展 M2M业务。由于 M2M业务与人与人之间的通信（ H2H, Human to Human ) 业务有明显的差异性， 因此需要对现有的网络进行必要的优化， 以获得最 佳的网络管理与网络通信质量。
第三代合作伙伴计划 （3GPP, 3rd Generation Partnership Project )现网 主要釆用 GPRS 网络实现数据包的传输， 随着无线宽带技术的发展， 业务 层对传输层的带宽、 时延等性能要求越来越高。 为提高其网络性能， 降低 网络建设及运营成本， 并在与其它无线接入技术， 如全球微波互联接入
( WiMax, Worldwide Interoperability for Microwave Access ) 的竟争中取得 优势， 3GPP开始致力于***架构演进（ SAE, System Architecture Evolution ) 的研究， 目的是使得演进的分组网 （EPC, Evolved Packet Core )可提供更 高的传输速率、 更短的传输延时、 优化分组， 及支持全球陆地无线接入
( UTRAN, Universal Terrestrial Radio Access )、演进的 UTRAN( E-UTRAN )、 无线局域网（WLAN, Wireless Local Area Network )及其他非 3 GPP的接入 网络之间的移动性管理。 SAE的架构如图 1所示， 其中， 演进的无线接入网 （E-RAN, Evolved Radio Access Network ) 中包含的网元有： 演进节点 B ( eNodeB, Evolved NodeB ), 用于为用户的接入提供无线资源； 分组数据网（PDN, Packet Data Network )用于为用户提供业务的网络； EPC提供了更低的延迟， 并允许更 多的无线接入***接入， 其包括如下网元：
移动管理实体（ MME , Mobility Management Entity ) , 是控制面功能实 体， 临时存储用户数据的服务器， 负责管理和存储用户设备（UE, User Equipment ) 的上下文（例如： 用户标识、 移动性管理状态、 用户安全参数 等）， 为用户分配临时标识， 当 UE驻扎在该跟踪区域或者该网络时， 负责 对该 UE的用户进行鉴权。
服务网关 （S-GW, Serving Gateway ), 是一个用户面实体， 负责用户 面数据路由处理， 终结处于空闲（ECM— IDLE )状态的 UE的下行数据。 管 理和存储 UE的 SAE承载（bearer )上下文， 例如： IP承载业务参数和网络 内部路由信息等。 S-GW是 3GPP***内部用户面的锚点， 一个用户在一个 时刻只能有一个 S-GW。
分组数据网网关 （ P-GW, PDN Gateway ), 是负责 UE接入 PDN的网 关，分配用户 IP地址，也是 3GPP和非 3GPP接入***的移动性锚点， P-GW 的功能还包括策略实施、 计费支持。 用户在同一时刻能够接入多个 P-GW。 策略与计费实施功能实体（ PCEF, Policy and Charging Enforcement Function ) 也位于 P-GW中。
策略与计费规则功能实体（ PCRF, Policy and Charging Rules Function ), 负责向 PCEF提供策略控制与计费规则。
归属用户服务器 （ HSS, Home Subscriber Server ), 负责永久存储签约 用户数据， HSS 存储的内容包括 UE 的国际移动用户识别码 （IMSI , International Mobile Subscriber Identification )、 P-GW的 IP地址。 机器类通信月良务器（ MTC Server, Machine Type Communication Server), 是为 M2M应用新增的网元，主要负责对机器类通信设备（ MTC UE , Machine Type Communication Device ) 的信息釆集和数据存储 /处理等工作， 并可对 MTC UE进行必要的管理。
MTC UE是 M2M业务使用的终端， 与 UE类似， 也包括通用集成电路 卡 （UICC , Universal Integrated Circuit Card ) 和移动设备（ME, Mobile Equipment ),通常负责收集若干釆集器的信息并通过 RAN节点接入核心网， 并与 MTC Server交互数据。
在图 1中， MTC UE需要通过 SAE网络向 MTC Server或其它的 MTC UE传输数据信息。 SAE网络为此次传输建立 S-GW与 P-GW之间的 GPRS 隧道协议（GTP, GPRS Tunneling Protocol )隧道， 数据信息通过 GTP隧道 实现可靠传输。
图 2是现有技术中， MTC UE接入到 EPS网络， 执行网络附着、 IP承 载建立的过程， 包括以下步骤：
步骤 201 , MTC UE为了接入到 SAE网络， 向 eNodeB发起网络附着 请求， 在其中携带了 IMSI、 MTC UE的网络接入能力、 请求分配 IP的指示 等信息。
步骤 202, eNodeB为 MTC UE选择一个为之服务的 MME, 并将附着 请求转发到该 MME,同时将 MTC UE的标识等重要信息也携带给该 MME。
步骤 203 , MME向 HSS发送鉴权数据请求消息（含 IMSI ), HSS首先 判断 IMSI对应的签约用户数据， 如果查找不到任何签约或者 IMSI已被列 入黑名单， 则 HSS向 MME返回鉴权数据响应并携带合适的错误原因； 如 果找到 IMSI对应的签约用户数据，则 HSS向 MME返回鉴权数据响应消息 (含鉴权向量）。
MME执行鉴权流程以验证终端 IMSI的合法性， 并执行安全模式流程 以启用安全连接。
步骤 204 , MME向归属网的 HSS发送位置更新请求， 其中携带 MME 的标识、 MTC UE的标识， 用以将 MTC UE当前所接入的区域告知 HSS。
步骤 205 , HSS根据 MTC UE的标识查找出 MTC UE的签约用户数据， 并将该签约用户数据发送给 MME。签约用户数据中主要包含缺省接入点名 称（APN, Access Point Name ), 带宽大小等信息。
MME接收到签约用户数据，检查 MTC UE是否被允许接入到网络，向 HSS返回接收用户响应； 若 MME发现 MTC UE有漫游限制或接入限制等 问题， MME将禁止 MTC UE附着， 并通知 HSS。
步骤 206 , HSS向 MME发送确认位置更新响应。
步骤 207, MME为 MTC UE选择一个 S-GW, 并向其发送建立默认承 载的请求。在该请求中， MME告知 S-GW必要的信息有： MTC UE的标识、 MME的标识、 为 MTC UE分配 IP地址的指示、 缺省带宽信息、 P-GW地 址等。
步骤 208 , S-GW向 P-GW发送建立默认承载的请求。在该请求中， S-GW 告知 P-GW必要的信息有： S-GW的地址、 缺省带宽信息、 为 MTC UE分 配 IP地址的指示等。
步骤 209, 如有必要， P-GW向 PCRF请求为该 MTC UE所配置的策略 和计费规则、 决策信息。
步骤 210, P-GW根据 PCRF返回的策略和计费决策信息， 建立缺省承 载， 并向 S-GW返回 7 载建立响应。
步骤 211 , S-GW向 MME发送默认承载建立的响应。
步骤 212, MME向 eNodeB发送附着接受响应 , 表明 MTC UE的附着 到网络的请求已被接受， 该响应中携带 S-GW 的地址与隧道端口标识 ( TEID , Tunnel Endpoint Identifier )。 步骤 213 , eNodeB保存 S-GW的地址与 TEID, 并向 MTC UE发送无 线承载建立请求， 要求 MTC UE保存承载建立的重要信息， 并开放相应的 端口。 在无线承载建立请求中， 携带了承载网络 ID、 P-GW的地址、 分配 给 MTC UE的 IP地址、 带宽信息等。
步骤 214, MTC UE向 eNodeB发送无线承载建立响应， 表明无线承载 建立完成。
步骤 215 , eNodeB 通知 MME 附着过程完成， 且在通知消息中携带 eNodeB的 TEID与 eNodeB的地址。
步骤 216, MME向 S-GW发送更新承载请求， 通知为 MTC UE服务的 eNodeB的 TEID和地址， 在 eNodeB与 S-GW之间建立起基于 GTP协议的 S1接入承载。
步骤 217, S-GW向 MME发送更新承载响应。
步骤 218, 如果 P-GW不是 HSS指定的， 则 MME向 HSS发送位置更 新请求， 通知给 HSS为 MTC UE所服务的 P-GW的地址信息， HSS更新该 信息。
M2M业务是以机器终端智能交互为核心的、 网络化的应用与服务。 它 釆用智能机器终端， 通过无线网络传输信息， 为客户提供的信息化解决方 案， 用于满足客户对监控、 指挥调度、 数据釆集和测量等方面的信息化需 求。
M2M的通信对象为机器对机器， 可以是人与机器之间的通信， 机器与 服务器之间的通信， 不同智能终端之间的通信。 不同应用的 MTC UE具有 不同的特性， 如电梯等升降机设备具有低移动性、 只有分组交换业务（PS only, Packet Switched only )属性， 而监视、 警报设备除具有低移动性、 PS only外， 还具有低数据传输和高可用性等属性。 因此需要针对不同应用的 MTC UE进行不同的***优化， 可有效的对 MTC UE进行管理、 监控、 付 费等。
在现有的 GPRS与长期演进（ LTE, Long Term Evolution ) 网络中， 从 图 2的流程中可以看出， 现有技术仅针对 H2H终端实现附着， 建立承载过 程， 网络需要为每个终端都建立不同的 GTP承载来进行数据业务。 H2H终 端发展趋势是向全业务方向发展， 终端可以实现语音通话、 上网业务、 视 频业务等， 因此需要占用大量的网络带宽， 网络需要针对不同的终端建立 不同的承载进行带宽、 优先级等服务质量（QoS, Quality of Service )控制。
而对于 M2M终端，其业务类型与 H2H终端完全不同，经统计，有 90% 以上的 M2M终端以低移动性低数据量业务为主， 其占用的带宽与 H2H终 端相比微乎其微。 由于 90%以上的 M2M终端都是低数据量的属性，可能每 天的数据量不超过几百比特， 因此按照现有技术，针对每个 M2M终端建立 承载会占用大量的网络承载资源， 同时大量的 M2M终端频繁地进行附着、 建立承载、注销等操作，对 EPC网络而言也占用了大量的信令开销，而 SAE 网络的高带宽优势完全不能体现。 发明内容
有鉴于此， 本发明的主要目的在于提供一种公用承载建立的方法、 数 据传输方法和核心网络侧设备， 以解决规模巨大的 M2M 终端接入到网络 时， 会占用大量网络资源的问题。
为达到上述目的， 本发明的技术方案是这样实现的：
本发明所提供的一种公用承载建立的方法， 该方法包括：
核心网络侧设备为机器类通信组（MTC Group ) 内的机器到机器间的 通信（M2M )终端建立组公用承载资源；
在所述 MTC Group内的 M2M终端接入演进的分组网 （ EPC ) 时， 所 述核心网络侧设备为请求接入的 M2M终端分配所述组公用承载资源。
所述为 MTC Group内的 M2M终端建立组公用承载资源， 具体为： 所述核心网络侧设备上预留 MTC Group 的组公用承载资源， 在所述 MTC Group内的 M2M终端首次接入时， 所述核心网络侧设备激活所述预 留的组公用承载资源；
相应的， 所述在 MTC Group内的 M2M终端接入 EPC时， 为请求接入 的 M2M终端分配组公用承载资源， 具体为：
所述核心网络侧设备将已激活的所述组公用承载资源指派给所述 MTC Group内请求接入的 M2M终端。
所述为 MTC Group内的 M2M终端建立组公用承载资源 , 具体为： 所述核心网络侧设备上不预留 MTC Group的组公用承载资源， 在所述 MTC Group 内的 M2M 终端首次接入时， 所述核心网络侧设备创建所述 MTC Group的组公用承载资源；
相应的， 所述在 MTC Group内的 M2M终端接入 EPC时， 为请求接入 的 M2M终端分配组公用承载资源， 具体为：
所述核心网络侧设备将已创建的所述组公用承载资源指派给所述 MTC Group内请求接入的 M2M终端。
所述为请求接入的 M2M终端分配组公用承载资源， 具体为： 所述核心网络侧设备根据 M2M终端的接入请求中携带的 MTC Group 标识， 或者根据请求接入的 M2M终端的签约数据中是否包含 MTC Group 属性 , 识别所述 M2M终端是否属于 MTC Group；
如果属于， 则根据所述 MTC Group标识识别对应的组公用承载资源是 否已激活或创建， 如果已激活或创建， 则直接将已激活或创建的组公用承 载资源指派给所述 M2M 终端； 如果未激活和创建， 则激活或创建与所述 MTC Group标识对应的组公用承载资源， 并将激活或创建的组公用承载资 源指派给所述 M2M终端；
如果不属于， 则不为所述 M2M终端激活或创建组公用承载资源。 本发明还提供了一种数据传输方法， 该方法包括：
核心网络侧设备为 MTC Group内请求接入的 M2M终端分配公用承载 资源；
所述核心网络侧设备创建并存储所述 MTC Group内各 M2M终端的无 线接入网络承载通道与组公用承载通道的对应关系， 并依据所述对应关系 执行数据的上下行传输。
所述对应关系中包括： M2M终端的标识、 M2M终端的 IP地址、 MTC Group标识、 无线 7?ι载隧道端口标识、 公用 7?ι载隧道端口标识。
所述依据对应关系执行数据的上下行传输， 具体为：
所述 MTC Group内 M2M终端的上行数据包经无线接入网络承载通道 发送到所述核心网络侧设备时， 所述核心网络侧设备根据上行数据包中所 携带 M2M终端的标识或 IP地址， 查找所述对应关系中对应的公用 载隧 道端口标识， 并将所述上行数据包转发到对应的公用承载隧道端口；
所述核心网络侧设备接收到发往 MTC Group内 M2M终端的下行数据 包时， 根据 MTC Group内的 IP地址段识别下行数据包所属的 MTC Group 标识， 并将所述下行数据包转发到对应所述 MTC Group标识的公用承载隧 道端口上；所述核心网络侧设备依据下行数据包中所携带 M2M终端的标识 或 IP地址， 查找所述对应关系中对应的无线 载隧道端口标识， 并将所述 上行数据包转发到对应的无线承载隧道端口。
本发明还提供了一种核心网络侧设备， 包括： 移动管理实体（MME )、 服务网关 （S-GW )和分组数据网网关 （P-GW ), 其中，
所述 S-GW和 P-GW, 用于为 MTC Group内的 M2M终端建立组公用 承载资源；
所述 MME,用于接收 MTC Group内 M2M终端的接入请求，并向 S-GW 和 P-GW请求激活或创建组公用承载资源， 若组公用承载资源已建立， 则 将所述 S-GW和 P-GW为 MTC Group建立的组公用承载资源分配给请求接 入的 M2M终端。
所述 S-GW和 P-GW进一步用于，预留 MTC Group的组公用承载资源， 并在所述 MTC Group内的 M2M终端首次接入时， 激活所述预留的组公用 承载资源； 还用于将已激活的所述组公用承载资源指派给所述 MTC Group 内请求接入的任意 M2M终端。
所述 S-GW和 P-GW进一步用于， 不预留 MTC Group的组公用承载资 源 , 在所述 MTC Group内的 M2M终端首次接入时， 创建所述 MTC Group 的组公用承载资源； 还用于将已创建的所述组公用承载资源指派给所述 MTC Group内请求接入的任意 M2M终端。
所述 MME进一步用于， 根据 M2M 终端的接入请求中携带的 MTC Group标识， 或者根据请求接入的 M2M终端的签约数据中是否包含 MTC Group属性， 识别所述 M2M终端是否属于 MTC Group；
如果属于， 则根据所述 MTC Group标识识别对应的组公用承载资源是 否已激活或创建， 如果已激活或创建， 则直接将已激活或创建的组公用承 载资源指派给所述 M2M终端； 如果未激活和创建， 则请求 S-GW和 P-GW 激活或创建与所述 MTC Group标识对应的组公用承载资源， 并将激活或创 建的组公用承载资源指派给所述 M2M终端；
如果不属于， 则不为所述 M2M终端激活或创建组公用承载资源。
所述 S-GW进一步用于， 创建并存储所述 MTC Group内各 M2M终端 的无线接入网络承载通道与组公用承载通道的对应关系， 所述对应关系中 包括： M2M终端的标识、 M2M终端的 IP地址、 MTC Group标识、 无线承 载隧道端口标识、 公用 载隧道端口标识。
所述 S-GW进一步用于 , 在接收到所述 MTC Group内 M2M终端经无 线接入网络承载通道发送的上行数据包时， 根据上行数据包中所携带 M2M 终端的标识或 IP地址，查找所述对应关系中对应的公用 7 载隧道端口标识， 并将所述上行数据包转发到对应的公用承载隧道端口。
所述 P-GW进一步用于 , 在接收到发往 MTC Group内 M2M终端的下 行数据包时， 根据 MTC Group内的 IP地址段识别下行数据包所属的 MTC Group标识， 并将所述下行数据包转发到对应所述 MTC Group标识的公用 承载隧道端口上；
相应的， 所述 S-GW进一步用于， 在接收到来自所述 P-GW的下行数 据包时， 依据下行数据包中所携带 M2M终端的标识或 IP地址， 查找所述 对应关系中对应的无线承载隧道端口标识， 并将所述上行数据包转发到对 应的无线承载隧道端口。
本发明所提供的一种公用承载建立的方法、 数据传输方法和核心网络 侧设备， 在签约时根据同地域或同属一个用户等原则， 将数量巨大但数据 量低的 M2M终端划为多个 MTC Group , 网络为每个 MTC Group建立组内 设备共用的公用承载， 这样既节省了网络资源， 减少不必要的频繁创建、 注销承载的开销； 而且多个设备共享资源， 还有效防止了 EPS高带宽承载 的低效性， 保证了网络资源的合理分配与公用承载的使用效率。 附图说明
图 1为现有技术中 EPS网络***的架构示意图；
图 2为现有技术中 MTC UE附着到 EPS网络的流程图；
图 3为本发明一种公用承载建立的方法流程图；
图 4为本发明实施例一中 MTC UE附着到 EPS网络的流程图； 图 5为本发明实施例二中 MTC UE附着到 EPS网络的流程图； 图 6为本发明实施例三中 MTC UE附着到 EPS网络的流程图； 图 7为本发明实施例四中 MTC UE附着到 EPS网络的流程图。 具体实施方式
下面结合附图和具体实施例对本发明的技术方案进一步详细阐述。 本发明为解决数量巨大的 M2M终端接入到网络时，占用大量网络资源 的问题， 对 M2M终端接入网络按 MTC组（ MTC Group )进行优化。 一种 基于 MTC Group优化的公用承载建立的方法， 如图 3所示， 主要包括以下 步骤：
步骤 301 , 核心网络侧设备为 MTC Group内的 M2M终端建立组公用 承载资源。
步骤 302, 在 MTC Group内的 M2M终端接入 EPC时， 核心网络侧设 备为请求接入的 M2M终端分配组公用承载资源。
组公用承载资源的具体建立和分配方式， 可以有以下两种：
第一种方式： 预先按 MTC Group在网络的相关网元中预留组公用承载 资源 , 当 MTC Group内的 M2M终端首次接入到网络时 , 激活网络预留的 组公用承载资源； 当 MTC Group内有后续 M2M终端接入到网络时 , 在附 着流程中将已经激活的组公用承载资源指派给 MTC Group 内所述接入的 M2M终端， 使 MTC Group内的设备接入后可共享组公用承载资源以实现 M2M业务。 例如： 一个 MTC Group内有四个 M2M终端 A、 B、 C、 D , 如 果该 MTC Group内首次接入到网络的 M2M终端为终端 A, 那么在终端 A 接入时， 激活网络为该 MTC Group预留的组公用承载资源， 并将激活的公 用承载资源分配给终端 A; 当后续有终端 B接入到网络时， 在终端 B的附 着流程中将已经激活的公用承载资源直接指派给终端 B即可； 同样的， 当 后续有终端 C或 D接入到网络时，在终端 C或 D的附着流程中将已经激活 的公用承载资源直接指派给终端 C或 D即可。
第二种方式： 预先不在网络的相关网元中预留 MTC Group内的组公用 承载资源， 当 MTC Group内的 M2M终端首次接入到网络时， 核心网络侧 设备为该 MTC Group创建组公用承载资源； 当 MTC Group内有后续 M2M 终端接入到网络时， 在附着流程中将已建立的组公用承载资源指派给 MTC Group内所述接入的 M2M终端， 使 MTC Group内的设备接入后可共享组 公用承载资源以实现 M2M业务。 例如： 一个 MTC Group内有四个 M2M 终端 A、 B、 C、 D , 如果该 MTC Group内首次接入到网络的 M2M终端为 终端 A, 那么在终端 A接入时 , 核心网络侧设备为该 MTC Group创建组公 用承载资源， 并将创建的组公用承载资源分配给终端 A; 当后续有终端 B 接入到网络时， 在终端 B的附着流程中将已建立的公用承载资源直接指派 给终端 B即可； 同样的， 当后续有终端 C或 D接入到网络时， 在终端 C或 D的附着流程中将已建立的公用承载资源直接指派给终端 C或 D即可。
较佳的 , 核心网络侧设备接收到 M2M终端的接入请求时 , 根据 M2M 终端的接入请求中携带的 MTC Group标识， 或者根据请求接入的 M2M终 端的签约数据中是否包含 MTC Group属性， 来识别 M2M终端是否属于 MTC Group;
如果属于， 则根据 MTC Group标识识别对应的组公用承载资源是否激 活或创建， 如果已经激活或创建， 则直接将已经激活或创建的组公用承载 资源指派给 M2M终端； 如果未激活和创建， 则激活或创建与 MTC Group 标识对应的组公用承载资源 , 并指派给 M2M终端；
如果不属于， 则无需为 M2M终端激活或创建组公用承载资源。
需要指出的是， 上述两种方式都是在 EPC的核心网络侧为 MTC Group 建立公用的承载通道， 但在无线接入技术（ RAT, Radio Access Technology ) 无线网络侧， 还需要为每个 M2M终端单独建立终端到 eNodeB的无线承载 通道， 以及 eNodeB到 S-GW的接入承载通道，该无线承载通道和接入承载 通道可以统称为无线接入网络承载通道。 因此， 需要在 S-GW创建并保存 MTC Group内各 M2M终端的无线接入网络承载通道与组公用承载通道的 对应关系 , 对应关系中可包含 M2M终端的标识 （ ID )、 M2M终端的 IP地 址、 MTC Group标识、 无线承载隧道端口标识、 公用承载隧道端口标识等 信息。 MTC Group内各 M2M终端的上行数据包经无线接入网络承载通道 发给 S-GW时， S-GW根据上述对应关系，通过数据包中的 M2M终端的 ID 或 IP地址， 为该上行数据包找到对应的网络侧公用承载通道， 并将上行数 据包转发到公用承载隧道端口。 MTC Group内各 M2M终端的下行数据包 发给 P-GW时， P-GW可以通过 MTC Group内 IP地址段识别下行数据包属 于 MTC Group内设备， 于是将该下行数据包转发到所对应的 MTC Group 的公用承载隧道端口上； 下行数据包到 S-GW时， S-GW根据 M2M终端的 ID或 M2M终端的 IP地址、 设备的无线接入网络承载通道与公用承载通道 的对应关系， 将下行数据包转发到对应的无线承载隧道端口。
下面再结合具体实施例对上述公用承载建立的方法进一步详细阐述。 本发明的实施例一如图 4所示， 网络为已签约的 MTC Group在相关网 元中预留组公用承载资源，当 MTC Group内 M2M终端首次接入到网络时， 网络激活 MTC Group的组公用承载资源，完成组内共享的公用承载的建立。 另外， 在 S-GW中需要创建并保存 MTC Group内各 M2M终端的无线接入 网络 载通道与核心网络侧组内公用承载通道的对应关系。 该实施例的具 体流程如下：
步骤 401 , M2M终端 （即图 4 中所示的 MTC UE )在签约时签约了 MTC Group标识（即 MTC Group ID ), MTC Group可以根据同属一个行业 用户， 或同属一个区域等原则签署。
在 EPC网络中签约了多个 MTC Group, EPC网络根据网络管理配置服 务器等配置工具，在 S-GW与 P-GW上为各 MTC Group预留以 MTC Group 为单位的公用承载资源， 如隧道流量模板 ( TFT, Tunnel Flow Template )端 口、 S-GW地址与 TEID、 P-GW地址与 TEID、 组 QoS规则等资源。 步骤 402, 属于 MTC Group的 MTC UE首次接入到 EPS网络时， 向 eNodeB发起网络附着请求，该请求中携带了 IMSI、MTC Group ID, MTC UE 的网络接入能力、 请求分配 IP的指示等信息。
需要指出的是， MTC UE的 IP地址可以静态配置， 也可以通过域名系 统（DNS, Domain Name System )服务器获取到动态分配的 IP地址。 MTC Group ID用以指示该 MTC UE属于此 ID标识的 MTC Group。
步骤 403 , eNodeB为 MTC UE选择一个为之服务的 MME, 并将附着 请求转发到该 MME, 同时将 MTC UE的标识、 MTC Group ID等重要信息 也携带给该 MME。
步骤 404, MME执行鉴权流程， 然后向归属网的 HSS发送位置更新请 求， 其中携带 MME的标识、 MTC UE的标识。
HSS根据 MTC UE的标识查找出 MTC UE的签约用户数据并发送给 MME。签约用户数据中主要包含缺省 APN、带宽大小等信息；还包含 MTC Group ID, 用以指示该 MTC UE属于哪一个 Group。
步骤 405 , MME接收到签约用户数据， 检查 MTC UE是否被允许接入 到网络， 若 MME发现 MTC UE有漫游限制或接入限制等问题， MME将禁 止 MTC UE附着， 并通知 HSS。
若 MTC UE没有接入等限制， MME根据 MTC UE在附着消息中携带 的 MTC Group ID,或根据在签约用户数据中的 MTC Group ID,查找该 MTC Group ID对应的组公用承载是否已激活。若是 MTC Group内终端首次接入， 组公用承载没有激活， 则 MME向 S-GW发送 MTC Group的组公用承载激 活请求，其中携带 MTC Group ID、分配的组公用承载 ID ( MTC Group LID ) 等信息。
步骤 406, S-GW收到 MTC Group的组公用承载激活请求后， 如果发 现 MTC Group的组公用承载已被激活， 则直接跳到步骤 407; 如果 MTC Group的组公用承载没有激活， 则激活为 MTC Group ID预留的 S-GW的 TEID端口， 配置 P-GW侧对应的 TEID端口， 并将激活组公用 载请求发 给 P-GW, 其中携带 MTC Group ID、 MTC Group LID等信息。 P-GW激活 为 MTC Group ID预留的 TFT端口及 TEID端口， 并配置 S-GW侧对应的 TEID端口， 分配组 QoS , 并通知给 S-GW已激活预留的组公用承载资源， 此时核心网络侧为 MTC Group ID预留的公用承载通道已激活。
步骤 407, 公用承载激活后， S-GW向 MME发送激活公用承载响应给 MME,其中携带 MTC Group LID、 P-GW的地址、 S-GW的地址、 S-GW TEID 等信息， 指示组公用承载已激活。
步骤 408, MME关联 MTC Group ID、 MTC Group LID、 S-GW的地址、
S-GW TEID的对应关系， 并向 eNodeB发送附着接受消息， 表明 MTC UE 的附着到网络的请求已被接受； 该消息中携带 MTC Group LID、 P-GW的 地址、 S-GW的地址、 S-GW TEID等信息。
步骤 409, eNodeB向 MTC UE发送无线承载建立请求， MTC UE保存 承载建立的 QoS等相关信息，并开放相应的 TFT端口。在该请求中携带有： 无线承载 ID、 P-GW地址、 带宽信息等。
MTC UE向 eNodeB发送无线 载建立完成消息， MTC UE与 eNodeB 已建立无线 载通道， 并釆用无线 载 ID进行标识。
步骤 410, eNodeB向 MME发送附着完成消息，其中携带 eNodeB TEID、 eNodeB地址等信息， 通知 MME附着过程完成。
步骤 411 , MME向 S-GW发送更新承载请求， 其中携带 MTC UE的标 识、 MTC Group LID , 并通知 S-GW为 MTC UE服务的 eNodeB的 TEID、 eNodeB的地址等信息。
步骤 412, S-GW根据 MTC Group LID识别是更新组公用承载的上下 行地址与端口， 则保存 MTC UE的标识 /MTC UE的 IP地址、 MTC Group LID, eNodeB TEID、 S-GW TEID的对应关系， 当 MTC UE发送或接收上 下行数据包时可以才艮据 MTC UE的标识或 MTC UE的 IP地址识别 ,根据上 述对应关系将数据包转发到相应的端口。
步骤 413 , S-GW向 MME发送更新承载响应， 表明 eNodeB到 S-GW 的 GTP隧道（ S1用户面接入承载 ) 已建立成功， MTC UE可以通过 S-GW 发送或接收上下文数据包。
本发明的实施例二如图 5所示， 网络已为 MTC Group激活预留的组公 用承载资源， 建立 MTC Group的组公用承载， 当 MTC Group内其它 M2M 终端接入到网络时， 网络直接将已建立的组公用承载指派给发起附着申请 的 M2M终端。 另外， 在 S-GW中需要创建并保存 MTC Group内各个接入 的 M2M 终端的无线接入网络承载通道与核心网络侧组内公用承载通道的 对应关系。 该实施例的具体流程如下：
步骤 501 , MTC Group中的 M2M终端首次接入时， MME向 S-GW请 求激活公用承载， S-GW/P-GW为 MTC Group激活 TFT端口、 S-GW地址 与 TEID、 P-GW地址与 TEID、 组 QoS规则等资源， MTC Group预留的公 用承载资源被激活， S-GW与 P-GW之间由 MTC Group LID标识的组公用 承载可以为 MTC Group内设备所共用。
步骤 502, 属于该 MTC Group的其它 MTC UE接入到 EPS网络时， 向 eNodeB发起网络附着请求， 在其中携带了 IMSI、 MTC Group ID、 MTC UE 的网络接入能力等信息。
需要指出的是， MTC UE的 IP地址可以静态配置， 也可以通过 DNS 服务器获取到动态分配的 IP地址。 MTC Group ID指示 MTC UE属于该 ID 标识的 MTC Group。
步骤 503 , eNodeB将附着请求转发到该 MME, 同时将 MTC UE的标 识、 MTC Group ID等重要信息也携带给该 MME。 步骤 504, MME执行鉴权流程， 然后向归属网的 HSS发送位置更新请 求， 其中携带 MME的标识、 MTC UE的标识。 HSS根据 MTC UE的标识 查找出 MTC UE的签约用户数据并发送给 MME。签约用户数据中主要包含 APN、 带宽大小等信息， 还包含 MTC Group ID。
步骤 505 , MME接收到用户签约用户数据， 检查 MTC UE是否被允许 接入到网络， 若 MME发现 MTC UE有漫游限制或接入限制等问题 , MME 将禁止 MTC UE附着， 并通知 HSS。
若 MTC UE没有接入等限制， MME根据 MTC UE在附着消息中携带 的 MTC Group ID , 或根据在签约用户数据中的 MTC Group ID , 查找 MTC Group ID对应的组公用承载是否已激活。 若组公用承载已激活， MME从 MTC Group的关联数据中找到 MTC Group LID、 P-GW的地址、 S-GW的 地址、 S-GW TEID , 并向 eNodeB发送附着接受消息， 表明 MTC UE的附 着到网络的请求已被接受。
后续步骤 506~510的操作与图 4所示实施例一中步骤 409~413的操作 相同， 此处不再赘述。
本发明的实施例三如图 6所示， MTC Group的组公用承载需要在 MTC Group中的 M2M终端首次接入时创建。 另外， 在 S-GW中需要创建并保存 MTC Group内各个接入的 M2M终端的无线接入网络承载通道与核心网络 侧的组公用 载通道的对应关系。 该实施例的具体流程如下：
步骤 601 , 属于 MTC Group的 MTC UE首次接入到 EPS网络时， 向 eNodeB发起网络附着请求， 在其中携带了 IMSI、 MTC Group ID、 MTC UE 的网络接入能力、 请求分配 IP的指示等信息。
需要指出的是， MTC UE的 IP地址可以静态配置， 也可以通过 DNS 服务器获取到动态分配的 IP地址。
步骤 602, eNodeB为 MTC UE选择一个为之服务的 MME, 并将附着 请求转发到该 MME, 同时将 MTC UE的标识、 MTC Group ID等重要信息 也携带给该 MME。
步骤 603 , MME执行鉴权流程， 然后向归属网的 HSS发送位置更新请 求， 其中携带 MME的标识、 MTC UE的标识。 HSS根据 MTC UE的标识 查找出 MTC UE的签约用户数据并发送给 MME。签约用户数据中主要包含 APN、 带宽大小等信息， 还包含 MTC Group ID。
MME接收到用户签约数据， 检查 MTC UE是否被允许接入到网络， 若 MME发现 MTC UE有漫游限制或接入限制等问题， MME将禁止 MTC UE附着， 并通知 HSS。
步骤 604, 若 MTC UE没有接入等限制， MME根据 MTC UE在附着 消息中携带的 MTC Group ID , 或根据在签约数据中的 MTC Group ID , 查 找 MTC Group ID对应的组公用承载是否已创建。 若是 MTC Group内终端 首次接入， 组公用承载没有创建， 则 MME向 S-GW发送创建组公用承载 请求， 该请求中携带 MTC UE的标识、 MTC Group ID、 MTC Group LID、 P-GW地址等信息。
步骤 605， S-GW收到组公用承载创建请求后， 如果发现组公用承载已 被创建，则直接跳到步骤 608向 MME发送创建组公用承载响应消息；如果 组公用承载未被创建， 则 S-GW为组公用承载创建一个新的入口， 然后向 P-GW发送创建 MTC Group的组公用承载请求。 在该请求中， S-GW告知 P-GW的必要信息有： MTC Group LID、 S-GW的地址与 TEID、 缺省带宽 信息等。
步骤 606, 如有必要， P-GW向 PCRF请求为该 MTC Group所配置的 QoS策略和计费规则， PCRF将 MTC Group对应的 PCC规则下发给 P-GW。
步骤 607, P-GW根据 PCRF返回的策略和计费决策信息， 为此 MTC Group建立组公用承载，并向 S-GW返回组公用承载建立响应，该响应中携 带 MTC Group公用承载标识、 P-GW的地址与 TEID信息。
步骤 608, S-GW更新并保存与 MTC Group标识对应的 MTC Group LID , P-GW的地址与 TEID等信息， S-GW到 P-GW的 GTP公用隧道建立 成功。组公用承载创建后， S-GW向 MME发送创建组公用承载响应给 MME, 该响应中携带 MTC Group LID、 P-GW的地址、 S-GW的地址、 S-GW TEID 等信息， 指示公用承载已创建。
后续步骤 609~614的操作与图 4所示实施例一中步骤 408~413的操作 相同， 此处不再赘述。
本发明的实施例四如图 7所示， 网络已为 MTC Group创建组公用承载 资源 , 建立了 MTC Group的组公用承载； 当 MTC Group其它 M2M终端接 入到网络时， 网络直接将已建立的组公用承载指派给发起附着申请的 M2M 终端。 另夕卜， 在 S-GW中需要创建并保存 MTC Group内各 M2M终端的无 线接入网络承载通道与核心网络侧的组内公用承载通道的对应关系。 该实 施例的具体流程如下：
步骤 701 , MTC Group中的 M2M终端首次接入时， MME请求创建 MTC Group的组公用承载， S-GW/P-GW收到组公用承载创建请求后， 为 MTC Group分配了 TFT端口、 S-GW地址与 TEID、 P-GW地址与 TEID等 资源， 成功创建了 S-GW与 P-GW之间由 MTC Group LID标识的组公用 承载。
步骤 702, 属于 MTC Group的其它 MTC UE接入到 EPS网络时， 向 eNodeB发起网络附着请求， 在其中携带了 IMSI、 MTC Group ID、 MTC UE 的网络接入能力等信息。
需要指出的是， MTC UE的 IP地址可以静态配置， 也可以通过 DNS 服务器获取到动态分配的 IP地址。
步骤 703 , eNodeB将附着请求转发到该 MME, 同时将 MTC UE的标 识、 MTC Group ID等重要信息也携带给该 MME。
步骤 704, MME执行鉴权流程， 然后向归属网的 HSS发送位置更新请 求， 其中携带 MME的标识、 MTC UE的标识。 HSS根据 MTC UE的标识 查找出 MTC UE的签约用户数据并发送给 MME。签约用户数据中主要包含 APN、 带宽大小等信息， 还包含 MTC Group ID。
步骤 705 , MME接收到用户签约数据， 检查 MTC UE是否被允许接入 到网络， 若 MME发现 MTC UE有漫游限制或接入限制等问题， MME将禁 止 MTC UE附着， 并通知 HSS。
若 MTC UE没有接入等限制， MME根据 MTC UE在附着消息中携带 的 MTC Group ID , 或根据在签约用户数据中的 MTC Group ID , 查找 MTC Group ID对应的组公用承载是否已创建。 若组公用承载已创建， MME从 MTC Group的关联数据中找到 MTC Group LID、 P-GW的地址、 S-GW的 地址、 S-GW TEID , 并向 eNodeB发送附着接受消息， 表明 MTC UE的附 着到网络的请求已被接受。
步骤 706, eNodeB向 MTC UE发送无线承载建立请求， MTC UE保存 承载建立的 QoS等相关信息， 并开放相应的 TFT端口。 在该无线承载建立 请求中携带有： 无线承载 ID、 P-GW地址、 带宽信息等。
MTC UE向 eNodeB发送无线 载建立完成消息， MTC UE与 eNodeB 已建立无线承载通道， 釆用无线承载 ID进行标识。
步骤 707 , eNodeB向 MME发送附着完成消息， 消息中携带 eNodeB TEID、 eNodeB地址等信息， 通知 MME附着过程完成。
步骤 708, MME向 S-GW发送更新承载请求， 其中携带 MTC UE的标 识、 MTC Group LID , 并通知 S-GW为 MTC UE服务的 eNodeB的 TEID、 eNodeB的地址等信息。
步骤 709, S-GW根据 MTC Group LID识别是更新组公用承载的上下 行地址与端口， 则保存 MTC UE的标识 /MTC UE的 IP地址、 MTC Group LID, eNodeB TEID、 S-GW TEID的对应关系， 当 MTC UE发送或接收上 下行数据包时可以才艮据 MTC UE的标识或 MTC UE的 IP地址识别 ,根据上 述对应关系将数据包转发到相应的端口。
步骤 710, S-GW向 MME发送更新承载响应， 表明 eNodeB到 S-GW 的 GTP隧道（ S1用户面接入承载 ) 已建立成功， MTC UE可以通过 S-GW 发送或接收上下文数据包。
本发明中用以实现上述公用承载建立的方法， 以及数据传输方法的核 心网络侧设备由： MME、 S-GW和 P-GW组成， 其中， S-GW和 P-GW, 用 于为 MTC Group 内的 M2M终端建立组公用承载资源； MME, 用于接收 MTC Group内 M2M终端的接入请求， 并向 S-GW和 P-GW请求激活或创 建组公用承载， 若组公用承载已建立， 则将 S-GW和 P-GW为 MTC Group 建立的组公用承载资源分配给请求接入的 M2M终端。
较佳的， S-GW和 P-GW进一步用于， 预留 MTC Group的组公用承载 资源， 并在 MTC Group内的 M2M终端首次接入时， 激活预留的组公用承 载资源； 还用于将已激活的组公用承载资源指派给 MTC Group内请求接入 的任意 M2M终端。 或者， S-GW和 P-GW不预留 MTC Group的组公用承 载资源， 在 MTC Group内的 M2M终端首次接入时， 创建 MTC Group的组 公用承载资源； 还用于将已创建的组公用承载资源指派给 MTC Group内请 求接入的任意 M2M终端。
较佳的， MME进一步用于，根据 M2M终端的接入请求中携带的 MTC Group标识， 或者根据请求接入的 M2M终端的签约数据中是否包含 MTC Group属性，识别 M2M终端是否属于 MTC Group;如果属于，则根据 MTC Group标识识别对应的组公用承载资源是否激活或创建，如果已经激活或创 建， 则直接将激活或创建的组公用承载资源指派给 M2M终端； 如果未激活 和创建， 则请求 S-GW和 P-GW激活或创建与 MTC Group标识对应的组公 用承载资源， 并指派给 M2M终端； 如果不属于， 则无需为 M2M终端激活 或创建组公用承载资源。
较佳的， S-GW进一步用于， 创建并存储 MTC Group内各 M2M终端 的无线接入网络承载通道与组公用承载通道的对应关系， 该对应关系中包 括： M2M终端的标识、 M2M终端的 IP地址、 MTC Group标识、 无线承载 隧道端口标识、 公用 载隧道端口标识。
S-GW在接收到 MTC Group内 M2M终端经无线接入网络承载通道发 送的上行数据包时，根据上行数据包中所携带 M2M终端的标识或 IP地址， 查找对应关系中对应的公用承载隧道端口标识， 并将上行数据包转发到对 应的公用承载隧道端口。
P-GW在接收到发往 MTC Group内 M2M终端的下行数据包时， 根据 MTC Group内的 IP地址段识别下行数据包所属的 MTC Group标识， 并将 下行数据包转发到对应 MTC Group标识的公用承载隧道端口上； 相应的， S-GW在接收到来自 P-GW的下行数据包时，依据下行数据包中所携带 M2M 终端的标识或 IP地址 , 查找对应关系中对应的无线 载隧道端口标识 , 并 将上行数据包转发到对应的无线承载隧道端口。
综上所述， 本发明在签约时根据同地域或同属一个用户， 将数量巨大 但数据量低的 M2M终端划为多个 MTC Group , 网络为每个 MTC Group建 立组内设备共用的公用承载， 这样既节省了网络资源， 减少不必要的频繁 创建、 注销承载的开销； 而且多个设备共享资源， 还有效防止了 EPS高带 宽承载的低效性， 保证了网络资源的合理分配与公用承载的使用效率。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种公用承载建立的方法， 其特征在于， 该方法包括：
核心网络侧设备为机器类通信组（MTC Group ) 内的机器到机器间的 通信（M2M )终端建立组公用承载资源；
在所述 MTC Group内的 M2M终端接入演进的分组网 （ EPC ) 时， 所 述核心网络侧设备为请求接入的 M2M终端分配所述组公用承载资源。
2、 根据权利要求 1 所述公用承载建立的方法， 其特征在于， 所述为 MTC Group内的 M2M终端建立组公用承载资源 , 具体为：
所述核心网络侧设备上预留 MTC Group 的组公用承载资源， 在所述 MTC Group内的 M2M终端首次接入时， 所述核心网络侧设备激活所述预 留的组公用承载资源；
相应的， 所述在 MTC Group内的 M2M终端接入 EPC时， 为请求接入 的 M2M终端分配组公用承载资源， 具体为：
所述核心网络侧设备将已激活的所述组公用承载资源指派给所述 MTC Group内请求接入的 M2M终端。
3、 根据权利要求 1 所述公用承载建立的方法， 其特征在于， 所述为 MTC Group内的 M2M终端建立组公用承载资源 , 具体为：
所述核心网络侧设备上不预留 MTC Group的组公用承载资源， 在所述 MTC Group 内的 M2M 终端首次接入时， 所述核心网络侧设备创建所述 MTC Group的组公用承载资源；
相应的， 所述在 MTC Group内的 M2M终端接入 EPC时， 为请求接入 的 M2M终端分配组公用承载资源， 具体为：
所述核心网络侧设备将已创建的所述组公用承载资源指派给所述 MTC Group内请求接入的 M2M终端。
4、 根据权利要求 1、 2或 3所述公用承载建立的方法， 其特征在于， 所述为请求接入的 M2M终端分配组公用承载资源， 具体为： 所述核心网络侧设备根据 M2M终端的接入请求中携带的 MTC Group 标识， 或者根据请求接入的 M2M终端的签约数据中是否包含 MTC Group 属性 , 识别所述 M2M终端是否属于 MTC Group；
如果属于， 则根据所述 MTC Group标识识别对应的组公用承载资源是 否已激活或创建， 如果已激活或创建， 则直接将已激活或创建的组公用承 载资源指派给所述 M2M 终端； 如果未激活和创建， 则激活或创建与所述 MTC Group标识对应的组公用承载资源， 并将激活或创建的组公用承载资 源指派给所述 M2M终端；
如果不属于， 则不为所述 M2M终端激活或创建组公用承载资源。
5、 一种数据传输方法， 其特征在于， 该方法包括：
核心网络侧设备为 MTC Group内请求接入的 M2M终端分配公用承载 资源；
所述核心网络侧设备创建并存储所述 MTC Group内各 M2M终端的无 线接入网络承载通道与组公用承载通道的对应关系， 并依据所述对应关系 执行数据的上下行传输。
6、 根据权利要求 5所述数据传输方法， 其特征在于， 所述对应关系中 包括： M2M终端的标识、 M2M终端的 IP地址、 MTC Group标识、 无线承 载隧道端口标识、 公用 载隧道端口标识。
7、 根据权利要求 5或 6所述数据传输方法， 其特征在于， 所述依据对 应关系执行数据的上下行传输， 具体为：
所述 MTC Group内 M2M终端的上行数据包经无线接入网络承载通道 发送到所述核心网络侧设备时， 所述核心网络侧设备根据上行数据包中所 携带 M2M终端的标识或 IP地址， 查找所述对应关系中对应的公用 载隧 道端口标识， 并将所述上行数据包转发到对应的公用承载隧道端口； 所述核心网络侧设备接收到发往 MTC Group内 M2M终端的下行数据 包时， 根据 MTC Group内的 IP地址段识别下行数据包所属的 MTC Group 标识， 并将所述下行数据包转发到对应所述 MTC Group标识的公用承载隧 道端口上；所述核心网络侧设备依据下行数据包中所携带 M2M终端的标识 或 IP地址， 查找所述对应关系中对应的无线 载隧道端口标识， 并将所述 上行数据包转发到对应的无线承载隧道端口。
8、 一种核心网络侧设备， 其特征在于， 包括： 移动管理实体（MME )、 服务网关 （S-GW )和分组数据网网关 （P-GW ), 其中，
所述 S-GW和 P-GW, 用于为 MTC Group内的 M2M终端建立组公用 承载资源；
所述 MME,用于接收 MTC Group内 M2M终端的接入请求，并向 S-GW 和 P-GW请求激活或创建组公用承载资源， 若组公用承载资源已建立， 则 将所述 S-GW和 P-GW为 MTC Group建立的组公用承载资源分配给请求接 入的 M2M终端。
9、 根据权利要求 8所述核心网络侧设备， 其特征在于， 所述 S-GW和 P-GW进一步用于， 预留 MTC Group的组公用承载资源， 并在所述 MTC Group内的 M2M终端首次接入时， 激活所述预留的组公用承载资源； 还用 于将已激活的所述组公用承载资源指派给所述 MTC Group内请求接入的任 意 M2M终端。
10、 根据权利要求 8所述核心网络侧设备， 其特征在于， 所述 S-GW 和 P-GW进一步用于，不预留 MTC Group的组公用承载资源，在所述 MTC Group内的 M2M终端首次接入时， 创建所述 MTC Group的组公用承载资 源； 还用于将已创建的所述组公用承载资源指派给所述 MTC Group内请求 接入的任意 M2M终端。
11、 根据权利要求 8、 9或 10所述核心网络侧设备， 其特征在于， 所 述 MME进一步用于， 根据 M2M终端的接入请求中携带的 MTC Group标 识， 或者根据请求接入的 M2M终端的签约数据中是否包含 MTC Group属 性 , 识别所述 M2M终端是否属于 MTC Group；
如果属于， 则根据所述 MTC Group标识识别对应的组公用承载资源是 否已激活或创建， 如果已激活或创建， 则直接将已激活或创建的组公用承 载资源指派给所述 M2M终端； 如果未激活和创建， 则请求 S-GW和 P-GW 激活或创建与所述 MTC Group标识对应的组公用承载资源， 并将激活或创 建的组公用承载资源指派给所述 M2M终端；
如果不属于， 则不为所述 M2M终端激活或创建组公用承载资源。
12、 根据权利要求 8、 9或 10所述核心网络侧设备， 其特征在于， 所 述 S-GW进一步用于， 创建并存储所述 MTC Group内各 M2M终端的无线 接入网络承载通道与组公用承载通道的对应关系， 所述对应关系中包括： M2M终端的标识、 M2M终端的 IP地址、 MTC Group标识、 无线承载隧道 端口标识、 公用 载隧道端口标识。
13、 根据权利要求 12所述核心网络侧设备， 其特征在于， 所述 S-GW 进一步用于， 在接收到所述 MTC Group内 M2M终端经无线接入网络承载 通道发送的上行数据包时，根据上行数据包中所携带 M2M终端的标识或 IP 地址， 查找所述对应关系中对应的公用承载隧道端口标识， 并将所述上行 数据包转发到对应的公用承载隧道端口。
14、 根据权利要求 12所述核心网络侧设备， 其特征在于， 所述 P-GW 进一步用于， 在接收到发往 MTC Group内 M2M终端的下行数据包时， 根 据 MTC Group内的 IP地址段识别下行数据包所属的 MTC Group标识， 并 将所述下行数据包转发到对应所述 MTC Group 标识的公用承载隧道端口 上；
相应的， 所述 S-GW进一步用于， 在接收到来自所述 P-GW的下行数 据包时， 依据下行数据包中所携带 M2M终端的标识或 IP地址， 查找所述 对应关系中对应的无线承载隧道端口标识， 并将所述上行数据包转发到对 应的无线承载隧道端口。
PCT/CN2010/077744 2009-11-23 2010-10-14 公用承载建立的方法、数据传输方法和核心网络侧设备 WO2011060673A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910238237.2 2009-11-23
CN200910238237.2A CN102076028B (zh) 2009-11-23 2009-11-23 公用承载建立的方法、数据传输方法和核心网络侧设备

Publications (1)

Publication Number Publication Date
WO2011060673A1 true WO2011060673A1 (zh) 2011-05-26

Family

ID=44034334

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/077744 WO2011060673A1 (zh) 2009-11-23 2010-10-14 公用承载建立的方法、数据传输方法和核心网络侧设备

Country Status (2)

Country Link
CN (1) CN102076028B (zh)
WO (1) WO2011060673A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021215973A1 (en) * 2020-04-20 2021-10-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangements relating to group transmission in a wireless communication network

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102740397B (zh) * 2011-04-07 2015-08-19 华为技术有限公司 一种多个终端接入的控制方法、控制设备、终端及***
WO2013004077A1 (zh) * 2011-07-05 2013-01-10 中兴通讯股份有限公司 一种建立安全通道的方法及相应终端和***
CN102355744B (zh) * 2011-09-29 2015-07-15 电信科学技术研究院 一种eps承载服务控制方法及mme
CN102355702B (zh) * 2011-09-29 2017-09-08 中兴通讯股份有限公司 支持机器类通信mtc终端的***配置方法及装置
CN102547867B (zh) * 2011-12-14 2014-11-05 北京邮电大学 公共承载建立方法
CN103249084B (zh) * 2012-02-07 2017-12-26 中兴通讯股份有限公司 终端触发方法及装置
WO2014000157A1 (en) * 2012-06-26 2014-01-03 Nokia Siemens Networks Oy Mtc device provisioning
CN103748859B (zh) 2012-07-23 2017-04-26 华为技术有限公司 一种数据传输方法、***及其设备
CN103906023B (zh) * 2012-12-28 2019-06-18 中兴通讯股份有限公司 机器类型设备mtc设备的触发信息的处理方法及装置
CN103974379A (zh) * 2013-01-24 2014-08-06 中兴通讯股份有限公司 设备到设备d2d发现授权处理方法及***
WO2014121493A1 (zh) * 2013-02-07 2014-08-14 华为技术有限公司 通信方法、通信装置和通信设备
CN104160745B (zh) * 2013-02-07 2018-05-18 华为技术有限公司 通信方法、通信装置和通信设备
CN104519597B (zh) * 2013-10-08 2018-10-30 阿尔卡特朗讯 一种用于设置承载的方法、装置和设备
CN104780577B (zh) * 2014-01-10 2018-07-24 ***通信集团公司 一种数据资源在小区间进行切换传输的方法和设备
CN104852994B (zh) * 2014-02-13 2018-03-23 普天信息技术研究院有限公司 一种终端侧分组数据网服务器地址管理方法
CN106817669B (zh) 2015-11-30 2021-05-04 华为技术有限公司 一种数据传输方法及***
CN106332311A (zh) * 2016-08-22 2017-01-11 广东工业大学 一种基于lte的物联网数据传输方法
CN108123853A (zh) * 2016-11-28 2018-06-05 中兴通讯股份有限公司 一种网络融合方法及终端
WO2018148861A1 (zh) 2017-02-14 2018-08-23 华为技术有限公司 下行数据的传输方法及装置
WO2019056169A1 (en) * 2017-09-19 2019-03-28 Nokia Shanghai Bell Co., Ltd. MODULATION AND CODING SCHEME (MCS) CORRECTION WHEN SHARING RADIO RESOURCES BETWEEN MTC AND NON-MTC
CN109842920B (zh) * 2017-09-28 2023-10-20 华为技术有限公司 一种传输方法、接入网设备和终端设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101094494A (zh) * 2006-06-19 2007-12-26 上海贝尔阿尔卡特股份有限公司 无线网络中用于对组用户进行无线接入控制的方法及设备
CN101176330A (zh) * 2005-03-24 2008-05-07 奥林奇股份有限公司 激活分组数据协议上下文的方法和***

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7680478B2 (en) * 2006-05-04 2010-03-16 Telefonaktiebolaget Lm Ericsson (Publ) Inactivity monitoring for different traffic or service classifications

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101176330A (zh) * 2005-03-24 2008-05-07 奥林奇股份有限公司 激活分组数据协议上下文的方法和***
CN101094494A (zh) * 2006-06-19 2007-12-26 上海贝尔阿尔卡特股份有限公司 无线网络中用于对组用户进行无线接入控制的方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE, 3GPP TSG-SA WG1 MEETING #48 S1-094063, 9 November 2009 (2009-11-09), Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG1_Serv/TSGS1_48_Beijing/tdocs/S1-094063.zip>> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021215973A1 (en) * 2020-04-20 2021-10-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangements relating to group transmission in a wireless communication network

Also Published As

Publication number Publication date
CN102076028B (zh) 2014-12-10
CN102076028A (zh) 2011-05-25

Similar Documents

Publication Publication Date Title
US11889465B2 (en) Paging cause value
US11991761B2 (en) Request to establish protocol data unit session with time sensitive network parameters
WO2011060673A1 (zh) 公用承载建立的方法、数据传输方法和核心网络侧设备
US11070627B2 (en) Discovery of a user plane function that supports cellular IoT optimization
US11737156B2 (en) Establishing a session or cellular Internet of Things packet transmission
EP4054254A1 (en) Core paging handling
EP2566199B1 (en) Method and system for transmitting small data packets
EP3253083B1 (en) Control method and device based on multiple priorities in wireless communication system
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和***
US20100309881A1 (en) Mobile communication system and tunnel management method thereof
WO2012051890A1 (zh) 终端接入限制的方法及***
WO2022001761A1 (zh) 通信方法及装置
WO2011026392A1 (zh) 一种路由策略的获取方法及***
US20110069659A1 (en) Method and apparatus for providing local breakout service in wireless communication system
WO2008128459A1 (fr) Procédé pour établir des supports par défaut de réseau sans fil et système pour celui-ci
WO2014209016A1 (en) Method and apparatus for offloading data traffic in a wireless communication system
WO2012024989A1 (zh) 承载释放方法及***
WO2012003781A1 (zh) 一种控制业务接纳的方法及***
WO2014071790A1 (zh) 固网移动融合的策略控制方法、装置及***
KR101526493B1 (ko) Ａｌｌ-ｉｐ 융합 네트워크를 위한 액세스 장치
WO2012129997A1 (zh) 本地访问连接的处理方法及装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10831088

Country of ref document: EP

Kind code of ref document: A1