WO2013056595A1 - 一种建立连接的方法、系统和设备 - Google Patents

一种建立连接的方法、系统和设备 Download PDF

Info

Publication number
WO2013056595A1
WO2013056595A1 PCT/CN2012/080345 CN2012080345W WO2013056595A1 WO 2013056595 A1 WO2013056595 A1 WO 2013056595A1 CN 2012080345 W CN2012080345 W CN 2012080345W WO 2013056595 A1 WO2013056595 A1 WO 2013056595A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
subscription configuration
configuration information
mtc device
network subscription
Prior art date
Application number
PCT/CN2012/080345
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 WO2013056595A1 publication Critical patent/WO2013056595A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a method, system, and device for establishing a connection.
  • LTE Long Term Evolution
  • the LTE system adopts a design method in which the user plane and the control plane are separated, and the control plane signaling and the user plane bearer are respectively separated by a separate network element MME (Mobile Management). Entity, Mobile Management Entity) and S-GW (Serving GW, Service Gateway) are responsible.
  • MME Mobile Management
  • S-GW Serving GW, Service Gateway
  • the main functions of the MME are NAS (Non Access Stratum) signaling establishment, NAS signaling security, signaling establishment across core networks, tracking services, roaming services, authorization and bearer management.
  • the S-GW is the gateway point for e B (evolved base station) handover, forwarding 2G / 3G and other system service gateway points, completing buffering of downlink packets, some initialization work, prescribed interception interception, packet routing and forwarding, etc. .
  • the P-GW (PDN GW, Packet Data Gateway) is used for policy enforcement, packet filtering, specified interception, address allocation, charging function, packet reproduction, and the like.
  • the control signaling between the UE (User Equipment) and the eNB and the core network is processed by the MME; the user data is transmitted to the P-GW through the S-GW, and then transmitted by the P-GW to various external APNs (Access Point Name, Access point name) node. Since the coupling of control signaling and user data is reduced, when a new service occurs, only the network element responsible for the user plane is upgraded, and the control information transmission is not affected, thereby greatly reducing the complexity of network maintenance and Equipment upgrade costs.
  • MTC Machine-to-machine
  • Machine control communication machine control communication
  • human-computer interaction communication mobile Connected communications to promote social production and lifestyle development. It is expected that the business of human-to-human communication in the future may only account for 1/3 of the entire terminal market, and a larger amount of communication is the MTC communication service.
  • MTC communication is also known as M2M (Machine-to-machine) communication or the Internet of Things.
  • SUMMARY Embodiments of the present application provide a method, system, and device for establishing a connection, which are used to reduce signaling overhead in a setup process before sending data to a network side, thereby improving system efficiency.
  • the access network device determines, by the core network device, the access network subscription configuration number of the MTC device that initiates the connection request;
  • the access network device determines, according to a preset correspondence between the access network subscription configuration number and the access network subscription configuration information, the access network subscription configuration information corresponding to the access network subscription configuration number of the MTC device;
  • the access network device establishes a connection with the MTC device according to the determined access network subscription configuration information.
  • the core network device determines an access network subscription configuration number of the MTC device that initiates the connection request to the access network device; the core network device sends the access network subscription configuration number to the access network device, to notify the The access network device establishes a connection with the MTC device according to the access network subscription configuration information corresponding to the access network subscription configuration number.
  • the MTC device initiates a connection request to the access network device
  • the MTC device establishes a connection with the access network device according to the corresponding access network subscription configuration information.
  • a determining module configured to determine, by the core network device, an access network subscription configuration number of the MTC device that initiates the connection request, and determine the MTC according to a preset correspondence between the preset access network subscription configuration number and the access network subscription configuration information. Access network subscription configuration information corresponding to the access network subscription configuration number of the device;
  • the first establishing module is configured to establish a connection with the MTC device according to the determined access network subscription configuration information.
  • a core network device for establishing a connection provided by the embodiment of the present application includes:
  • An established MTC device provided by the embodiment of the present application includes:
  • the second establishing module is configured to establish a connection with the access network device according to the corresponding access network subscription configuration information.
  • a system for establishing a connection provided by an embodiment of the present application includes:
  • An access network device configured to determine, by the core network device, an access network subscription configuration number of the MTC device that initiates the connection request, and determine, according to a preset correspondence between the access network subscription configuration number and the access network subscription configuration information, The access network subscription configuration information corresponding to the access network subscription configuration number of the MTC device is established, and the connection is established with the MTC device according to the determined access network subscription configuration information.
  • a core network device configured to determine an access network subscription configuration number of the MTC device that initiates a connection request to the access network device, and send the access network subscription configuration number to the access network device;
  • the MTC device is configured to initiate a connection request to the access network device, and establish a connection with the access network device according to the corresponding access network subscription configuration information.
  • FIG. 1 is a schematic structural diagram of a system for establishing a connection according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of an access network device according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a core network device according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an MTC device according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a method for establishing a connection on an access network device side according to an embodiment of the present application
  • FIG. 6 is a schematic flowchart of a method for establishing a connection by a device on a core network device according to an embodiment of the present application
  • FIG. 7 is a schematic flowchart of a method for establishing a connection on an MTC device side according to an embodiment of the present application
  • FIG. 8 is a schematic flowchart of a method for obtaining an access network subscription configuration information by using an MTC device in an LTE system according to an embodiment of the present application;
  • FIG. 9 is a schematic flowchart of a method for establishing an connection by using an access network subscription configuration information by an MTC device having only one access network subscription configuration information in an LTE system according to an embodiment of the present application;
  • FIG. 10 is a schematic flowchart of a method for establishing an connection by using an access network subscription configuration information by an MTC device having multiple sets of access network subscription configuration information in an LTE system according to an embodiment of the present application;
  • FIG. 11 is a schematic flowchart of a method for changing an access network subscription configuration information of an MTC device in an LTE system according to an embodiment of the present application
  • FIG. 12 is a schematic flowchart of a method for obtaining an access network subscription configuration information by using only one set of access network subscription configuration information in an UMTS according to an embodiment of the present disclosure
  • FIG. 13 is a schematic flowchart of a method for establishing a connection by using an access network subscription configuration information by an MTC device having only one access network subscription configuration information in the UMTS according to an embodiment of the present application;
  • FIG. 14 is a schematic flowchart of a method for changing an access network subscription configuration information of an MTC device in a UMTS according to an embodiment of the present invention
  • 15 is a schematic flowchart of a method for obtaining an access network subscription configuration information by using an MTC device with multiple sets of access network subscription configuration information in UMTS according to an embodiment of the present disclosure
  • 16 is a schematic flowchart of a method for establishing a connection by using an access network subscription configuration information by an MTC device having multiple access network subscription configuration information in a UMTS according to an embodiment of the present application;
  • FIG. 17 is a schematic flowchart of a method for changing an access network subscription configuration information of an MTC device in a UMTS according to an embodiment of the present invention.
  • the specific implementation manner is that the network needs to perform a complex signaling process for each MTC device to establish a DRB/RB and a Sl/Iu bearer, and then the data can be sent to the network side through the DRB/RB and the Sl/Iu bearer, which causes a letter.
  • the cost is relatively large, which reduces the problem of system efficiency.
  • the MTC USER negotiates with the network operator to determine an access network subscription configuration used by the MTC device, and stores the access network subscription configuration number used by each MTC device in the core network.
  • the access network queries the core network for the access network subscription configuration number of the MTC device, and the access network determines, according to the access network subscription configuration number, the corresponding access network subscription configuration information, and uses the access network subscription configuration.
  • the information establishes a connection for the MTC device.
  • the service characteristics are the same, and the same access network can be used to sign the configuration information.
  • the access network can establish a connection with the MTC device according to the access network subscription configuration information corresponding to the MTC device.
  • the RRC setup message is encapsulated in the manner of the access network subscription configuration, and the service bearer is simultaneously established in the RRC setup process, thereby omitting the process of establishing the service bearer later, and reducing the establishment before sending the data to the network side.
  • the signaling overhead in the process thereby improving system efficiency.
  • the access network subscription configuration information of the embodiment of the present application includes, but is not limited to, at least one of the following information: SRB (Signaling Radio Bearer) information, DRB (Data Radio Bearer) information, RB (Radio Bearer) information, PDCP (Packet Data Convergence Protocol) information, RLC (Radio Link Control) information, MAC (Medium Access Control) information, and Configuration parameters of the physical layer (antennaInfo, tpc, transmissionMode (transmission mode, such as LTE transmission mode), etc.).
  • SRB Signal Radio Bearer
  • DRB Data Radio Bearer
  • RB Radio Bearer
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • the subscription configuration parameters reduce the number of signaling of the RRC Connection Reconfiguration Signaling Procedure (LTE) and the RB Setup Process (UMTS), thereby reducing the signaling load.
  • LTE RRC Connection Reconfiguration Signaling Procedure
  • UMTS RB Setup Process
  • the solution of the embodiment of the present application can be applied to an LTE system and a UMTS (Universal Mobile Telecommunication System), and can also be applied to other systems that require an MTC device to establish a connection with an access network device.
  • UMTS Universal Mobile Telecommunication System
  • the system for establishing a connection in the embodiment of the present application includes: an access network device 10, a core network device 20, and
  • the access network device 10 is configured to determine, by the core network device 20, an access network subscription configuration number of the MTC device 30 that initiates the connection request, according to a preset correspondence between the access network subscription configuration number and the access network subscription configuration information.
  • the access network subscription configuration information corresponding to the access network subscription configuration number of the MTC device 30 is determined, and the connection is established with the MTC device 30 according to the determined access network subscription configuration information.
  • the core network device 20 is configured to determine an access network subscription configuration number of the MTC device 30 that initiates a connection request to the access network device 10, and send an access network subscription configuration number to the access network device 10;
  • the MTC device 30 is configured to initiate a connection request to the access network device 10, and establish a connection with the access network device 10 according to the corresponding access network subscription configuration information.
  • some MTC devices 30 correspond to one access network subscription configuration information, and some MTC devices 30 correspond to multiple access network subscription configuration information, which are respectively introduced below.
  • Case 1 The MTC device 30 corresponds to an access network subscription configuration information.
  • the MTC device 30 initiates a connection request including the device identifier of the MTC device 30 to the access network device when the connection needs to be initiated;
  • the access network device 10 sends the device identifier in the received connection request to the core network device 20;
  • the core network device 20 determines the access network subscription configuration number corresponding to the device identifier of the MTC device 30, and returns it to the access network device 10 according to the correspondence between the preset device identifier and the access network subscription configuration number;
  • the access network device 10 determines the access network subscription configuration information corresponding to the access network subscription configuration number of the MTC device 30 according to the preset correspondence between the access network subscription configuration number and the access network subscription configuration information, and notifies the MTC.
  • the device 30 initiates access network subscription configuration information.
  • the core network device 20 first needs to determine whether the corresponding MTC device 30 is a subscription user device (for example, a subscription user device), and if so, further determine a corresponding access network subscription configuration number. If not a subscriber, follow existing core network protocols 23.401 (LTE Core Network) and 23.060 (UMTS) The core network) is carried out in a prescribed process.
  • a subscription user device for example, a subscription user device
  • UMTS UMTS
  • the core network will not issue the subscription configuration number, so the access network will not deliver all the subscription configuration content.
  • the MTC device 30 uses the access network subscription configuration to establish a connection, the MTC device 30 initiates an RRC connection establishment.
  • the establishment reason for the subscription user is the M2M subscription user, and the non-licensed user does not use the reason, so the access network can be distinguished. Come.
  • the device identifier of the MTC device 30 is information that can uniquely identify an MTC device, including but not limited to one of the following information:
  • IMSI International Mobile Subscriber Identity
  • P-TMSI Packet-Temporary Mobile Subscriber Identification
  • S-TMSI SAE - Temporary Mobile Subscriber Identify, SAE Temporary Mobile Subscriber Identification Number
  • GUTI Globally Unique Temporary Identify
  • the core network device 20 can determine the corresponding IMSI according to P-TMSI or S-TMSI or GUTI.
  • the device that stores the subscription configuration number in the core network may be an MME (Mobility Management Entity), an S-GW, a P-GW, and an HSS (Home Subscriber Server). Contracted user server), intermediate node, etc.
  • MME Mobility Management Entity
  • S-GW Serving Mobility Management Entity
  • P-GW Packet Control Entity
  • HSS Home Subscriber Server
  • the device storing the subscription configuration number in the core network may be an SGSN (Serving GPRS Support Node), an HLR (Home Location Register), an intermediate node, or the like.
  • SGSN Server GPRS Support Node
  • HLR Home Location Register
  • intermediate node or the like.
  • Method 1 The MTC device 30 stores the access network subscription configuration information directly in the device before leaving the factory, that is, the MTC device 30 pre-stores the access network subscription configuration information.
  • the MTC device 30 does not pre-store the access network subscription configuration information, and the network side broadcasts through the system message, that is, when the MTC device 30 first accesses, the network notifies the MTC device 30 to sign the configuration number, and the MTC device 30 reads the broadcast.
  • the access network subscription configuration information for storage.
  • the core network device 20 does not store the access network subscription configuration information after determining that the MTC device 30 initiates a connection request to the access network device 10, and the MTC device 30 corresponds to an access network subscription configuration information, according to a preset.
  • the MTC device 30 corresponds to an access network subscription configuration information, according to a preset.
  • the access network device 10 determines, according to the correspondence between the access network subscription configuration number and the access network subscription configuration information, the access network subscription configuration information corresponding to the received access network subscription configuration number, and sends all access networks through broadcast. Signing the configuration information, and notifying the access network subscription configuration information belonging to the MTC device in the access network configuration information of the MTC device through the RRC signaling; The MTC device 30 stores the access network subscription configuration information corresponding to the MTC device notified by the access network device.
  • Mode 3 The MTC device 30 does not pre-store the access network subscription configuration information.
  • the complete information of the access network subscription configuration is transmitted to the MTC device through signaling.
  • the network can change the information of the access network subscription configuration through signaling.
  • the core network device 20 determines that the access network subscription configuration information is not stored by the MTC device 30 that initiates the connection request to the access network device 10, and the MTC device 30 corresponds to an access network subscription configuration information, according to a preset setting. Corresponding relationship between the device identifier and the access network subscription configuration number, determining an access network subscription configuration number corresponding to the device identifier of the MTC device 30, and transmitting the determined access network subscription configuration number to the access network device 10;
  • the access network device 10 determines, according to the correspondence between the access network subscription configuration number and the access network subscription configuration information, the access network subscription configuration information corresponding to the received access network subscription configuration number, and notifies the MTC device by using RRC signaling.
  • Access network subscription configuration information ;
  • the MTC device 30 stores the access network subscription configuration information corresponding to the MTC device notified by the access network device 10.
  • the access network subscription configuration information may be updated as needed, and two update methods are listed below.
  • the core network device 20 determines whether the MTC device has an update flag. If the MTC device has an update flag, the access network device 10 is notified of the access network subscription configuration corresponding to the access network subscription configuration information that is updated by the MTC device 30. Numbering;
  • the access network device 10 After receiving the access network subscription configuration number corresponding to the access network subscription configuration information that needs to be updated, the access network device 10 determines that the MTC device 30 has an update flag, and then subscribes to the access network according to the access network subscription configuration number. Corresponding relationship between the configuration information, determining the access network subscription configuration information corresponding to the received access network subscription configuration number, and initiating a paging notification to the MTC device to read the system message to the MTC device 30 that needs to perform the access network subscription configuration information update. And sending a system message including the updated access network subscription configuration information;
  • the MTC device 30 updates the stored access network subscription configuration information according to the received access network subscription configuration information that is updated from the access network device 10.
  • the core network device 20 determines whether the MTC device has an update flag. If the MTC device has an update flag, the access network device 10 is notified of the access network subscription configuration corresponding to the access network subscription configuration information that is updated by the MTC device 30. Numbering;
  • the access network device 10 After receiving the access network subscription configuration number corresponding to the access network subscription configuration information that needs to be updated, the access network device 10 determines that the MTC device 30 has an update flag, and then subscribes to the access network according to the access network subscription configuration number. Corresponding relationship of the configuration information, determining the access network subscription configuration information corresponding to the received access network subscription configuration number, and transmitting the dedicated signaling including the updated access network subscription configuration information when the MTC device 30 initiates the service request Notifying the MTC device 30 to update the corresponding access network subscription configuration information;
  • the MTC device 30 updates the stored access network subscription configuration information according to the received access network subscription configuration information that needs to be updated from the access network device 10.
  • the access network device 10 notifies the core network device to remove the update flag of the MTC device; the core network device 20 removes the MTC device. Update the tag.
  • the MTC device 30 corresponds to a plurality of access network subscription configuration information.
  • the MTC device 30 initiates, to the access network device 10, a connection request including the device identifier of the MTC device 30 and an internal subscription configuration sequence number corresponding to the access network subscription configuration information used for establishing the connection;
  • the access network device 10 sends the device identifier and the internal subscription configuration serial number in the received connection request to the core network device 20;
  • the core network device 20 determines the access network configuration number corresponding to the device identifier and the internal subscription configuration sequence number of the MTC device 30 according to the correspondence between the preset device identifier, the internal subscription configuration sequence number, and the access network subscription configuration number. And return to the access network device 10;
  • the access network device 10 determines the access network subscription configuration information corresponding to the access network subscription configuration number of the MTC device 30 according to the preset correspondence between the access network subscription configuration number and the access network subscription configuration information, and determines the subscription network subscription configuration information corresponding to the access network subscription configuration number of the MTC device 30.
  • the internal subscription configuration sequence number corresponding to the MTC device obtained by the core network device is sent to the MTC device, and is used to notify the MTC device to start the access network subscription configuration information corresponding to the internal subscription configuration sequence number.
  • the core network device 20 first needs to determine whether the corresponding MTC device 30 is a subscription user device (such as an M2M subscription user device). If yes, further determine the corresponding access network subscription configuration number. If not, proceed according to the procedures specified in the existing core network protocols 23.401 (LTE core network) and 23.060 (UMTS core network).
  • a subscription user device such as an M2M subscription user device.
  • the device identifier of the MTC device 30 is information that can uniquely identify an MTC device, including but not limited to one of the following information:
  • IMSI IMSI, P-TMSI, S-TMSI and GUTI.
  • the core network device 20 can determine the corresponding IMSI according to P-TMSI or S-TMSI or GUTI.
  • the device that stores the subscription configuration number in the core network may be any device that stores the subscription configuration number in the core network.
  • MME Mobility Management Entity
  • S-GW S-GW
  • P-GW P-GW
  • HSS intermediate node, etc.
  • the device storing the subscription configuration number in the core network may be an SGSN, an HLR, an intermediate node, or the like.
  • Method 1 The MTC device 30 stores the access network subscription configuration information directly in the device before leaving the factory, that is, the MTC device 30 pre-stores the access network subscription configuration information.
  • the MTC device 30 does not pre-store the access network subscription configuration information, and the network side broadcasts through the system message, that is, when the MTC device 30 first accesses, the network notifies the MTC device 30 to sign the configuration number, and the MTC device 30 reads the wide.
  • the corresponding access network subscription configuration information in the broadcast is stored.
  • the core network device 20 does not store the access network subscription configuration information after determining that the MTC device 30 initiates the connection request to the access network device 10, and the MTC device 30 corresponds to the plurality of access network subscription configuration information, according to the preset Corresponding relationship between the device identifier and the access network subscription configuration number, determining all access network subscription configuration numbers corresponding to the device identifier of the MTC device 30, and transmitting all the determined access network subscription configuration numbers to the access network device 10;
  • the access network device 10 determines the access network subscription configuration information corresponding to each received access network subscription configuration number according to the correspondence between the access network subscription configuration number and the access network subscription configuration information, and sends all the connections through the broadcast.
  • the network access subscription configuration information is sent, and the access network subscription configuration information belonging to the MTC device in the access network configuration information of the MTC device is notified by the RRC signaling;
  • the MTC device 30 establishes and stores the correspondence between the access network subscription configuration information and the internal subscription configuration sequence number according to the access network subscription configuration information corresponding to the MTC device notified by the access network device and the order of each access network subscription configuration information. relationship.
  • the MTC device 30 determines that the corresponding three access network subscription configuration information is 5, 8, and 9, and then determines the internal subscription configuration serial number corresponding to the fifth access network subscription configuration information. If yes, the internal subscription configuration sequence number corresponding to the eighth access network subscription configuration information is 1 and the internal subscription configuration sequence number corresponding to the ninth access network subscription configuration information is 2.
  • the internal subscription configuration serial number can be directly notified to the MTC device 30.
  • the core network device 20 determines, according to the preset correspondence between the device identifier, the internal subscription configuration sequence number, and the access network subscription configuration number, all internal subscription configuration serial numbers and access corresponding to the device identifier of the MTC device 30.
  • the network subscription configuration number is sent to the access network device 10 to determine the determined internal subscription configuration sequence number and the corresponding access network subscription configuration number;
  • the access network device 10 passes the access network subscription configuration information corresponding to all access network subscription configuration numbers and the internal subscription configuration serial number corresponding to the access network subscription configuration information of the core network device 20 for the MTC device 30. Broadcast is sent to the MTC device 30;
  • the MTC device 30 establishes and stores a correspondence between the access network subscription configuration information and the internal subscription configuration sequence number according to the received access network subscription configuration information and the corresponding internal subscription configuration sequence number.
  • Mode 3 The MTC device 30 does not pre-store the access network subscription configuration information.
  • the complete information of the access network subscription configuration is transmitted to the MTC device through signaling.
  • the network can change the information of the access network subscription configuration through signaling.
  • the core network device 20 determines that the MTC device 30 that initiates the connection request to the access network device 10 does not store the access network subscription configuration information, and after the MTC device 30 corresponds to the multiple access network subscription configuration information, according to the preset Corresponding relationship between the device identifier and the access network subscription configuration number, and determining all connections corresponding to the device identifier of the MTC device 30 Entering the network subscription configuration number, and sending the determined access network subscription configuration number to the access network device 10;
  • the access network device 10 determines the access network subscription configuration information corresponding to each received access network subscription configuration number according to the correspondence between the access network subscription configuration number and the access network subscription configuration information, and notifies the MTC through RRC signaling. All access network subscription configuration information corresponding to the device;
  • the MTC device 30 establishes and stores the access network subscription configuration information and the internal subscription configuration serial number according to the access network subscription configuration information corresponding to the MTC device 30 notified by the access network device 10 and the order of each access network subscription configuration information. Correspondence.
  • the MTC device 30 determines that the corresponding three access network subscription configuration information is 5, 8, and 9, and then determines the internal subscription configuration serial number corresponding to the fifth access network subscription configuration information. If yes, the internal subscription configuration sequence number corresponding to the eighth access network subscription configuration information is 1 and the internal subscription configuration sequence number corresponding to the ninth access network subscription configuration information is 2.
  • the internal subscription configuration serial number can be directly notified to the MTC device 30.
  • the core network device 20 determines, according to the preset correspondence between the device identifier, the internal subscription configuration sequence number, and the access network subscription configuration number, all internal subscription configuration sequence numbers and access networks corresponding to the device identifiers of the MTC device 30. Signing the configuration number, and sending the determined internal subscription configuration sequence number and the corresponding access network subscription configuration number to the access network device 10;
  • the access network device 10 compares the received access network subscription configuration information corresponding to the received access network subscription configuration number with the internal subscription configuration sequence corresponding to the access network subscription configuration information of the core network device 20 for the MTC device 30. No., sent to the MTC device 30 through an RRC message;
  • the MTC device 30 establishes and stores the correspondence between the access network subscription configuration information and the internal subscription configuration sequence number according to the received access network subscription configuration information and the internal subscription configuration sequence number.
  • the access network subscription configuration information may be updated as needed, where the update includes replacing the access network subscription configuration information and increasing the access network subscription configuration information.
  • the update includes replacing the access network subscription configuration information and increasing the access network subscription configuration information.
  • the core network device 20 determines whether the MTC device has an update flag. If the MTC device has an update flag, the access network device 10 is notified of the access network subscription configuration corresponding to the access network subscription configuration information that is updated by the MTC device 30. Number and internal contract configuration serial number;
  • the access network device 10 After receiving the access network subscription configuration number corresponding to the access network subscription configuration information that needs to be updated, the access network device 10 knows that the MTC device 30 has an update flag, and then signs the access network according to the access network subscription configuration number. Corresponding relationship between the configuration information, determining the access network subscription configuration information corresponding to the received access network subscription configuration number, and initiating a paging notification to the MTC device to read the system message to the MTC device 30 that needs to perform the access network subscription configuration information update. And sending a system message including the updated access network subscription configuration information and the internal subscription configuration serial number;
  • the MTC device 30 updates the stored connection according to the received access network subscription configuration information and the internal subscription configuration sequence number.
  • the network subscription configuration information and the corresponding internal subscription configuration serial number are included in the received access network subscription configuration information and the internal subscription configuration sequence number.
  • the core network device 20 determines whether the MTC device has an update flag. If the MTC device has an update flag, the access network device 10 is notified of the access network subscription configuration corresponding to the access network subscription configuration information that is updated by the MTC device 30. Number and internal contract configuration serial number;
  • the access network device 10 After receiving the access network subscription configuration number corresponding to the access network subscription configuration information that needs to be updated, the access network device 10 knows that the MTC device 30 has an update flag, and then signs the access network according to the access network subscription configuration number. Corresponding relationship between the configuration information, determining the access network subscription configuration information corresponding to the received access network subscription configuration number, and transmitting the subscription information including the updated access network configuration information and the corresponding internal when the MTC device 30 initiates the service request Signing the dedicated signaling of the configuration sequence number, and notifying the MTC device 30 to update the corresponding access network subscription configuration information;
  • the MTC device 30 updates the stored access network subscription configuration information and the corresponding internal subscription configuration sequence number according to the received access network subscription configuration information and the internal subscription configuration sequence number.
  • the access network device 10 After determining that the update of the MTC device 30 is completed (such as receiving an acknowledgment message returned by the MTC device 30), the access network device 10 notifies the core network device 20 to remove the update flag of the MTC device 30; the core network device 20 removes the MTC.
  • the update tag of device 30 is not notified.
  • a preferred method is to fuse the update process and the connection process, that is, when the access network device 10 needs to update the MTC device 30 that initiates the connection, the connection that needs to be updated may be connected.
  • the network access subscription configuration information is placed in the feedback information for the connection request of the MTC device 30.
  • the initial selected access network is used to sign the configuration information.
  • the subscription configuration information or the updated access network subscription configuration information is connected to the access network device (if the initially selected access network subscription configuration information is updated, the updated access network is directly used to sign configuration information and access. Network devices are connected).
  • the MTC device 30 if the MTC device 30 supports multiple access network subscription configuration information, the MTC device 30 establishes a correspondence between the access network subscription configuration information and the internal subscription configuration sequence number.
  • the internal subscription configuration sequence number has the same function as the access network subscription configuration number, and is used to identify the access network subscription configuration information, but the access network subscription configuration number is used for the access network device 10 to identify the access network.
  • the subscription configuration information; the role of the internal subscription configuration sequence number is to identify the access network subscription configuration information for the MTC device 30.
  • the access network device 10 does not recognize it after receiving it, but sends it to the MTC device 30.
  • the access network subscription configuration information is not required to be stored, but the correspondence between the identifier of the MTC device 30, the internal subscription configuration sequence number, and the access network subscription configuration number is stored, so that access can be made.
  • the access network subscription configuration information identified by the network device 10 and the MTC device 30 remains the same.
  • the internal subscription configuration sequence number and the access network subscription configuration number can be the same as needed, so that only A correspondence between the identifier of the MTC device 30 and the internal subscription configuration sequence number (or the access network subscription configuration number) is established.
  • the embodiment of the present application further provides an access network device, a core network device, an MTC device, and a method for establishing a connection.
  • the system and the method for solving the problem are connected with the embodiment of the present application.
  • the implementation of these devices and methods can be seen in the implementation of the system, and the details are not repeated here.
  • the access network device in this embodiment of the present application includes: a determining module 200 and a first establishing module 210.
  • the determining module 200 is configured to determine, by the core network device, an access network subscription configuration number of the MTC device that initiates the connection request, and determine the MTC device according to the preset correspondence between the access network subscription configuration number and the access network subscription configuration information. Access network subscription configuration information corresponding to the access network subscription configuration number;
  • the first establishing module 210 is configured to establish a connection with the MTC device according to the determined access network subscription configuration information.
  • the determining module 200 if the MTC device corresponds to an access network subscription configuration information, after determining the access network subscription configuration information, before establishing the connection with the MTC device, the determining module 200 notifies the MTC device to start the access network subscription configuration information;
  • the determining module 200 sends the internal subscription configuration sequence number corresponding to the MTC device acquired by the core network device to the MTC device. And configured to notify the MTC device to start the access network subscription configuration information corresponding to the internal subscription configuration sequence number.
  • the determining module 200 after determining that the MTC device that initiates the connection request does not store the access network subscription configuration information, sends all the access network subscription configuration information through the broadcast, and passes the RRC letter. And to notify the MTC device of all the access network subscription configuration information that belongs to the access network subscription configuration information of the MTC device; or
  • the MTC device Before determining the access network subscription configuration information, after determining that the MTC device that initiates the connection request does not store the access network subscription configuration number and the access network subscription configuration information, the MTC device is notified of the access network subscription configuration information corresponding to the MTC device.
  • the determining module 200 initiates a paging notification to the MTC device that needs to perform the update of the access network subscription configuration information, and the MTC device reads the system message, and sends a system message including the updated access network subscription configuration information; or
  • the MTC device When the MTC device initiates a service request, the MTC device is notified to update the corresponding access network subscription configuration information by sending a dedicated signaling that includes the updated access network subscription configuration information.
  • the determining module 200 determines the access network subscription configuration information that needs to be updated according to the following manner: the access network subscription configuration number corresponding to the access network subscription configuration information that is updated according to the received requirements from the core network device. After that, the corresponding access network subscription configuration information that needs to be updated is determined.
  • the determining module 200 receives the access network subscription configuration corresponding to the access network subscription configuration information that needs to be updated from the core network device before the MTC device updates the corresponding access network subscription configuration information by using dedicated signaling. After numbering, make sure the MTC device has an update flag. Preferably, the determining module 200 notifies the core network device to remove the update flag of the MTC device after the update is completed. Preferably, the determining module 200 forwards the internal subscription configuration sequence number corresponding to the access network subscription configuration information of the MTC device from the core network device to the MTC device.
  • the core network device in this embodiment of the present application includes: a processing module 300 and a sending module 310.
  • the processing module 300 is configured to determine an access network subscription configuration number of the MTC device that initiates a connection request to the access network device;
  • the sending module 310 is configured to send an access network subscription configuration number to the access network device, to notify the access network device to establish a connection with the MTC device according to the access network subscription configuration information corresponding to the access network subscription configuration number.
  • the processing module 300 determines the access network subscription configuration corresponding to the device identifier of the MTC device, according to the correspondence between the preset device identifier and the access network subscription configuration number. Numbering;
  • the processing module 300 determines the device identifier and the internal subscription configuration of the MTC device according to the correspondence between the preset device identifier, the internal subscription configuration sequence number, and the access network subscription configuration number.
  • the access network subscription configuration number corresponding to the serial number.
  • the processing module 300 determines the access network subscription configuration number after determining that the MTC device that initiates the connection request is the subscription user equipment.
  • the processing module 300 determines the MTC according to the correspondence between the preset device identifier and the access network subscription configuration number. And the device network identifier corresponding to the access network subscription configuration number, and sending the determined access network subscription configuration number to the access network device, configured to notify the access network device to configure the access corresponding to the access network subscription configuration number for the MTC device.
  • the network subscription configuration information; or the internal contract configuration sequence number and the access network subscription configuration number corresponding to the device identifier of the MTC device are determined according to the correspondence between the preset device identifier, the internal subscription configuration sequence number, and the access network subscription configuration number.
  • the processing module 300 notifies the access network device that the access network subscription configuration number corresponding to the updated access network subscription configuration information needs to be sent to the MTC device.
  • the processing module 300 sends the internal subscription configuration sequence number corresponding to the access network subscription configuration information of the MTC device to the access network device, and is used to notify the access network.
  • the device forwards the internal subscription configuration serial number to the MTC device.
  • the processing module 300 After determining that the MTC device has the update flag, the processing module 300 notifies the access network device that the access network subscription configuration number corresponding to the updated access network subscription configuration information needs to be sent to the MTC device.
  • the processing module 300 removes the update flag of the MTC device after the MTC device completes the update of the access network subscription configuration information.
  • the MTC device in this embodiment of the present application includes: a reporting module 400 and a second establishing module 410.
  • the reporting module 400 initiates a connection request to the access network device.
  • the second establishing module 410 is configured to establish a connection with the access network device according to the corresponding access network subscription configuration information.
  • the uplink module 400 sends a connection request including the corresponding device identifier of the MTC device to the access network device;
  • the reporting module 400 initiates a connection request for the internal subscription configuration sequence number corresponding to the access network subscription configuration information that is required to be used by the MTC device to the access network device. .
  • the reporting module 400 pre-stores the access network subscription configuration information.
  • the uplink module 400 does not store the access network subscription configuration information. If the MTC device corresponds to one access network subscription configuration information, the reporting module 400 stores the access network subscription configuration information corresponding to the MTC device notified by the access network device. The access module 400 does not store the access network subscription configuration information.
  • the reporting module 400 registers the configuration information according to the access network corresponding to the MTC device notified by the access network device, and each Establishing and storing the correspondence between the access network subscription configuration information and the internal subscription configuration sequence number in the order of the access network subscription configuration information; or the access network subscription configuration information and the internal subscription according to the MTC device notified by the access network device Configure the serial number, and establish and store the correspondence between the access network subscription configuration information and the internal subscription configuration serial number.
  • the reporting module 400 updates the stored access network subscription configuration information according to the received access network subscription configuration information that is updated from the access network device. If the MTC device corresponds to multiple access network subscription configuration information, the reporting module 400 updates the stored access network subscription information according to the received access network subscription configuration information and the internal subscription configuration sequence number that are updated from the access network device. Configuration information and corresponding internal contract configuration serial number.
  • the method for establishing a connection on the device side of the access network in the embodiment of the present application includes:
  • Step 501 The access network device determines, by the core network device, an access network subscription configuration number of the MTC device that initiates the connection request.
  • Step 502 The access network device determines, according to a preset correspondence between the access network subscription configuration number and the access network subscription configuration information, the access network subscription configuration information corresponding to the access network subscription configuration number of the MTC device.
  • Step 503 The access network device establishes a connection with the MTC device according to the determined access network subscription configuration information.
  • the method further includes:
  • the access network device notifies the MTC device to start the access network subscription configuration information
  • the access network device sends the internal subscription configuration sequence number corresponding to the MTC device that is obtained by the core network device to the MTC device, to notify the MTC device to start the internal subscription.
  • the method further includes:
  • the access network device After determining that the MTC device that initiates the connection request does not store the access network subscription configuration information, the access network device sends all the access network subscription configuration information through broadcast, and notifies the MTC device of all the access network subscription configuration information through RRC signaling. Access network subscription configuration information belonging to the MTC device; or
  • the access network device After determining that the MTC device that initiates the connection request does not store the access network subscription configuration number and the access network subscription configuration information, the access network device notifies the access network subscription configuration information corresponding to the MTC device by using the RRC signaling.
  • the access network device may also sign the access network for the MTC device from the core network device when configuring the access network subscription configuration information for the MTC device.
  • the internal subscription configuration sequence number corresponding to the configuration information is forwarded to the MTC device.
  • the embodiment of the present application may further update the access network subscription configuration information.
  • the access network device initiates a paging notification to the MTC device that needs to update the access network subscription configuration information, and the MTC device reads the system message, and sends a system message including the updated access network subscription configuration information; or
  • the access network device When the MTC device initiates a service request, the access network device notifies the MTC device to update the corresponding access network subscription configuration information by sending a dedicated signaling that includes the updated access network subscription configuration information.
  • the access network device determines, by the core network device, that the MTC device has an update flag, it determines to update the MTC device.
  • the access network device determines the access network subscription configuration information corresponding to the access network subscription configuration number of the core network device that needs to be updated for the MTC device.
  • the determined access network that needs to be updated is determined.
  • the subscription configuration information is sent to the MTC device.
  • the access network device notifies the core network device to remove the update flag of the MTC device.
  • the access network device may also perform the access network subscription configuration information for the MTC device from the core network device when updating the MTC device.
  • the internal subscription configuration serial number is forwarded to the MTC device.
  • the access network device has the following behavior:
  • the access network stores all types of access network subscription configurations
  • the initial MTC device initiates the establishment of the Mo-Signal RRCConnectionRequest message and carries the Attach in the RRCConnectionSetupComplete message.
  • the request (access request) message when the core network device receives the Attach Request of the MTC device configured by the access network subscription, sends the access network subscription configuration number used by the MTC device to the eNB, and the eNB obtains the access network subscription.
  • the RRC Connection Setup message is passed. Notify the MTC
  • the access network subscription configuration number of the standby network is used, and the access network subscription configuration information is sent to the MTC device together with other configuration information for the MTC device through RRC Connection Reconfiguration;
  • an establishment cause may be added to the RRC Connection Request message. After receiving the RRC Connection Request message of the establishment cause, the e B sends the access to the core network device.
  • the network subscription configuration query information where the identifier of the MTC device is carried. (If the MTC device corresponds to multiple access network subscription configuration query information, the corresponding internal subscription configuration serial number may also be carried);
  • the Setup message notifies the MTC device;
  • the access network subscription configuration information includes complete control plane and service plane configuration information, and the eNB does not need to establish a service RB for the MTC device again through the reconfiguration process;
  • the network side can control the update of the access network subscription configuration, and the eNB can notify the MTC device to update the access network subscription configuration by means of paging + system message, or can send an update through dedicated signaling when the MTC device initiates a service request. After the access network subscription configuration. If the access network subscription configuration is updated by the dedicated signaling, the core network needs to record whether the access network subscription configuration information of the MTC device is updated, and when the eNB queries the core network, notify the eNB that the eNB sends the updated MTC device to the MTC device. Updated access network subscription configuration information.
  • the access network device has the following behavior:
  • the access network stores all types of access network subscription configurations, and establishes a correspondence between the access network subscription configuration information and the access network subscription configuration number;
  • the RNC After receiving the RRC Connection Request message of the M2M subscription service, the RNC sends the access network subscription configuration query information to the core network device, where the RNC carries the MTC device identifier (if the MTC device corresponds to multiple access network subscription configuration query information) , can also carry the corresponding internal subscription configuration serial number);
  • the RNC receives the RAB Assignment Request message sent by the core network. If the message carries the configuration delivery indication, the RNC queries the corresponding access network subscription configuration according to the subscription configuration number, and sets the access network subscription configuration information through RB Setup. (Also may include an internal subscription configuration serial number) sent to the MTC device. It is also possible to broadcast the access network subscription configuration information in the system message;
  • the RNC receives the RAB Assignment Request message sent by the core network. If the message has a number update indication, the RNC learns that the access network subscription configuration information of the MTC device has been changed, and queries the corresponding access according to the access network subscription configuration number.
  • the network subscription configuration information may be notified by the paging + system message to update the MTC Device to the newly numbered access network subscription configuration, or the new numbered access network subscription configuration may be delivered through the RRC Connection Setup signaling;
  • the RNC receives the RAB Assignment Request message sent by the core network. If the message has neither the configuration indication nor the number update indication, the RNC queries the corresponding access network subscription configuration information according to the access network subscription configuration number.
  • the RRC Connection Setup message informs the MTC device that the message only carries the subscription network except the access network. Setting the per UE content, and then using the access network subscription configuration information to establish a context for the MTC Device;
  • the access network subscription configuration information includes the complete control plane and service plane configuration information. After the MTC device stores the access network subscription configuration information, the RNC does not need to establish the service RB for the MTC device again through the RB establishment process.
  • Step 601 The core network device determines an access network subscription configuration number of the MTC device that initiates the connection request to the access network device.
  • Step 602 The core network device sends an access network subscription configuration number to the access network device, to notify the access network device to establish a connection with the MTC device according to the access network subscription configuration information corresponding to the access network subscription configuration number.
  • step 601 if the MTC device corresponds to an access network subscription configuration information, the core network device determines the access corresponding to the device identifier of the MTC device according to the correspondence between the preset device identifier and the access network subscription configuration number. Web subscription configuration number;
  • the core network device determines the device identifier and the internal subscription configuration of the MTC device according to the correspondence between the preset device identifier, the internal subscription configuration sequence number, and the access network subscription configuration number.
  • the access network subscription configuration number corresponding to the serial number.
  • the core network device determines whether the MTC device that initiated the connection request is a subscription user device, and if yes, step 601 is performed.
  • the core network device determines, according to the correspondence between the preset device identifier and the access network subscription configuration number, the access network subscription corresponding to the device identifier of the MTC device.
  • the internal subscription configuration sequence number and the access network subscription configuration number are used to notify the access network device to configure the access network subscription configuration information and the internal subscription configuration sequence number corresponding to the access network subscription configuration number for the MTC device.
  • the core network device notifies the access network device that
  • the access network subscription configuration number corresponding to the updated access network subscription configuration information of the MTC device is not limited.
  • the core network device may also send the internal subscription configuration sequence number corresponding to the access network subscription configuration information of the MTC device to the access network device, and notify the access network device The internal subscription configuration serial number is forwarded to the MTC device.
  • the core network device removes the update flag of the MTC device after the MTC device completes the update of the access network subscription configuration information.
  • the core network has the following behavior:
  • the core network device stores the access network subscription configuration number and the number of all the MTC devices configured with the access network subscription configuration.
  • the department signs the configuration sequence number, and establishes a correspondence between the IMSI and the access network subscription configuration number, and a correspondence between the IMSI, the internal subscription configuration sequence number, and the access network subscription configuration number;
  • the core network device After receiving the Attach Request message, the core network device first checks whether the IMSI query corresponding to the S-TMSI is an M2M subscription user. If it is an M2M subscription user, the corresponding access network subscription configuration number is queried (if there is an internal subscription) Configure the serial number, and also need to search according to the internal subscription configuration sequence number. In the Initial Context Setup Request message, carry the subscription network access network subscription configuration number (if according to the internal subscription configuration sequence). The number is searched, preferably also carries the internal subscription configuration serial number), and the configuration indication information; if it is not the M2M subscription user, the information is not carried;
  • the core network device After the core network device receives the access network subscription configuration query message sent by e B, it firstly according to the IMSI corresponding to the S-TMSI (if there is an internal subscription configuration serial number, it is also necessary to search according to the internal subscription configuration serial number. Querying the corresponding access network subscription configuration number, and sending an Initial Context Setup Request message to the eNodeB, carrying the access network subscription configuration number;
  • the network side can update the access network subscription configuration information, that is, change the subscription user to another access network subscription configuration.
  • the core network device needs to record whether the access network configuration number of the MTC device has been changed, and mark it once.
  • the core network device finds that the change flag exists, and notifies the eNB of the changed access network subscription configuration number and number update indication by using the Initial Context Setup Request message;
  • the core network device receives the Initial Context Setup Response message, if the message carries the configuration delivery confirmation, the core network confirms that the MTC device has stored the access network subscription configuration.
  • the core network device receives the Initial Context Setup Response message, if the message carries the number update confirmation, and the core network device confirms that the MTC device has changed the access network subscription configuration, the change flag of the access network subscription configuration information is cleared.
  • the core network has the following behavior:
  • the core network device stores the access network subscription configuration number and the internal subscription configuration sequence number of all the MTC devices configured with the access network subscription, and establishes the correspondence between the IMSI and the access network subscription configuration number, and the IMSI and the internal subscription configuration. Correspondence between the serial number and the access network subscription configuration number;
  • the core network device After receiving the Attach Request message, the core network device first checks whether the IMSI query corresponding to the P-TMSI is the M2M subscription user. If it is an M2M subscription user, query the corresponding access network subscription configuration number (if there is an internal subscription configuration serial number, you need to search according to the internal subscription configuration serial number), in the RAB Assignment Request message. And carrying the access network subscription configuration number (if the internal subscription configuration serial number is used for searching, preferably carrying the internal subscription configuration serial number), and configuring the delivery instruction; if not the M2M subscription user, the information is not carried;
  • the core network device After the core network device receives the access network subscription configuration query message sent by the RNC, first according to the P-TMSI The corresponding IMSI (if there is an internal subscription configuration sequence number, it is also necessary to search according to the internal subscription configuration sequence number), query the corresponding access network subscription configuration number, and send an RAB Assignment Request message to the RNC, carrying the access network subscription configuration. Numbering;
  • the network side can control the access network subscription configuration, and change the M2M subscription user to another access network subscription configuration. That is, the core network device needs to record whether the access network configuration number of the MTC device has been changed, and the change is marked once.
  • the core network device queries the core network device, the core network device finds that the change flag exists, and notifies the RNC of the changed access network subscription configuration number and number update indication by using the RAB Assignment Request message;
  • the core network device receives the RAB Assignment Response message, if the message carries the configuration delivery confirmation, the core network confirms that the UE has stored the access network subscription configuration.
  • the core network device receives the RAB Assignment Response message, if the message carries the number update confirmation, and the core network confirms that the MTC device has changed the access network subscription configuration, the change flag of the access network subscription configuration is cleared.
  • Step 701 The MTC device initiates a connection request to the access network device.
  • Step 702 The MTC device establishes a connection with the access network device according to the corresponding access network subscription configuration information.
  • step 701 the ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇
  • the MTC device If the MTC device corresponds to an access network subscription configuration information, the MTC device initiates a connection request including the corresponding device identifier of the MTC device to the access network device;
  • the MTC device If the MTC device corresponds to multiple access network subscription configuration information, the MTC device sends a connection request to the access network device that includes the corresponding device identifier of the MTC device and the internal subscription configuration sequence number corresponding to the access network subscription configuration information used to establish the connection.
  • the MTC device may pre-store access network subscription configuration information.
  • the method further includes: if the MTC device corresponds to one access network subscription configuration information, the MTC device stores the access network subscription configuration corresponding to the MTC device notified by the access network device.
  • the MTC device If the MTC device corresponds to multiple access network subscription configuration information, the MTC device establishes and stores access according to the access network subscription configuration information corresponding to the MTC device notified by the access network device and the order of each access network subscription configuration information. Corresponding relationship between the network subscription configuration information and the internal subscription configuration sequence number; or establishing and storing the access network subscription configuration information and internal information according to the access network subscription configuration information and the internal subscription configuration sequence number corresponding to the MTC device notified by the access network device The correspondence between the subscription configuration serial numbers.
  • the MTC device updates the stored access network subscription configuration information according to the received access network subscription configuration information that is updated from the access network device.
  • the MTC device receives the access according to the received The network device needs to update the access network subscription configuration information and the corresponding internal subscription configuration sequence number, and update the stored access network subscription configuration information and the corresponding internal subscription configuration serial number.
  • the MTC device determines the access network subscription configuration information that needs to be updated according to the order of the access network subscription configuration information or the received internal subscription configuration sequence number.
  • the MTC device has the following behavior:
  • the RRC Connection Request message with the reason mo-Signalling is initiated.
  • the MTC device After receiving the RRC Connection Setup message/RRC Connection Reconfiguration message containing the access network subscription configuration information, the MTC device saves the access network subscription configuration.
  • the MTC device that stores the access network subscription configuration needs to perform service transmission, then initiates
  • An MTC device that supports multiple access network subscription configuration information may carry an internal access network subscription configuration sequence number when initiating an access;
  • the MTC device can directly use the access network subscription configuration to perform signaling and data transmission. If the received RRC Connection Setup message has complete access network subscription configuration information, it is updated. Stored access network subscription configuration.
  • the MTC device After receiving the paging (page) for notifying the change of the subscription configuration information of the access network, the MTC device reads the system information and updates the stored access network subscription configuration information.
  • the MTC device has the following behavior:
  • the new establishment cause - M2M subscription service is used in the RRC Connection Request
  • the MTC device After receiving the RB Setup containing the access network subscription configuration information and other configuration information for itself, the MTC device saves the access network subscription configuration. If there are multiple access network subscription configurations, the MTC device saves the received access network subscription configuration and the corresponding internal subscription configuration serial number, and establishes the correspondence between the access network subscription configuration and the internal subscription configuration serial number. Relationship
  • the RRC Connection Setup message can directly use the stored access network subscription configuration; if the RRC Connection Setup message is used, If there is complete access network subscription configuration information, the stored access network subscription configuration is updated and used;
  • the MTC device that supports multiple access network subscription configuration information may carry an internal subscription configuration sequence number when initiating access. If only the per UE content except the access network subscription configuration is received in the received RRC Connection Setup message, the MTC device directly uses the associated stored one according to the internal subscription configuration sequence number when the access is initiated. Access network subscription configuration; if there is complete access network subscription configuration information in the RRC Connection Setup message, the MTC device updates its associated stored access network subscription configuration according to the internal subscription configuration sequence number when initiating the access, and uses ;
  • the MTC device After receiving the paging (page) for notifying the change of the subscription configuration information of the access network, the MTC device reads the system information and updates the stored access network subscription configuration information.
  • the method for obtaining the access network subscription configuration information by using the signaling by the MTC device of the LTE system in the embodiment of the present application includes the following steps:
  • Step 801 The UE sends an RRC Connection Request message with the establishment cause mo-Signalling and including the S-TMSI to the e B.
  • Step 802 The eNB returns an RRC Connection Setup message to the UE.
  • Step 803 The UE sends an RRC Connection Setup Complete message and a NAS Attach Request message to the eNB.
  • Step 804 The eNB sends a NAS Attach Request message including an S-TMSI to the MME.
  • Step 805 The MME performs Authentication/NAS Security Mode Control on the UE corresponding to the S-TMSI.
  • Step 806 After determining that the UE is a subscription user of the M2M, the MME determines an access network subscription configuration number corresponding to the UE, and returns an Initial Context Setup Request message and an NAS including the access network subscription configuration number to the eNB. Attach Accept message;
  • Step 807 The eNB searches for the corresponding access network subscription configuration information according to the access network subscription configuration number.
  • Step 808 The eNB sends an AS Security Mode Command message to the UE.
  • Step 809 The UE returns an AS Security Mode Complete message to the eNB.
  • Step 810 The eNB sends the message to the UE.
  • Step 811 The UE stores the received access network subscription configuration information.
  • Step 812 The UE sends an RRC Connection Reconfiguration Complete message to the eNB.
  • Step 813 The eNB sends an Initial Context Setup Response message to the MME.
  • Step 814 The UE sends a NAS Attach Complete message to the eNB.
  • Step 815 The eNB sends a NAS Attach Complete message to the MME.
  • step 806 and step 810 may further carry a corresponding internal subscription configuration sequence number.
  • the method for establishing an connection by using an access network subscription configuration information by an MTC device having only one set of access network subscription configuration information in the LTE system of the present application includes the following steps: Step 901: The UE sends an RRC Connection Request message including the S-TMSI to the eNB. Step 902: The eNB sends an access network subscription configuration query message including the S-TMSI to the MME.
  • Step 903 The MME determines, according to the S-TMSI, an access network subscription configuration number corresponding to the UE, and returns an Initial Context Setup Request message including an access network subscription configuration number to the eNB.
  • Step 904 The eNB searches for the corresponding access network subscription configuration information according to the access network subscription configuration number, and establishes a context for the UE according to the access network subscription configuration information.
  • Step 905 The eNB sends an RRC Connection Setup message to the UE.
  • step 906 the eNB sends an AS Security Mode Command message to the UE.
  • step 907 the UE returns an AS Security Mode Complete message to the eNB.
  • Step 908 The UE and the eNB enable the access network subscription configuration information.
  • Step 909 The UE sends an RRC Connection Setup Complete message to the eNB.
  • Step 910 The eNB sends an Initial Context Setup Complete message to the MME.
  • the eNB may further carry the content of the AS Security Mode Command message in the RRC Connection Setup message in step 905; correspondingly, in step 909, the UE may also be in the RRC Connection Setup Complete message. The content of the AS Security Mode Complete message is carried.
  • the method for establishing an connection by using an access network subscription configuration information by an MTC device having multiple access network subscription configuration information in an LTE system includes the following steps:
  • Step 1001 The UE sends an RRC Connection Request message including an S-TMSI and an internal subscription configuration sequence number corresponding to the access network configuration information that needs to be enabled to the eNB.
  • Step 1002 The eNB sends an access network subscription configuration query message including an S-TMSI and an internal subscription configuration sequence number to the MME.
  • Step 1003 The MME determines an access network subscription configuration number corresponding to the UE according to the S-TMSI and the internal subscription configuration sequence number, and returns an Initial Context Setup Request message including the access network subscription configuration number to the eNB.
  • Step 1004 The eNB accesses according to the access The network subscription configuration number is used to search for the corresponding access network subscription configuration information, and establish a context for the UE according to the access network subscription configuration information;
  • Step 1005 The eNB sends an RRC Connection Setup message to the UE.
  • step 1006 the eNB sends an AS Security Mode Command message to the UE.
  • step 1007 the UE returns an AS Security Mode Complete message to the eNB.
  • Step 1008 The eNB enables the access network subscription configuration information, and the UE enables the access network subscription configuration information corresponding to the internal subscription configuration sequence number.
  • Step 1009 The UE sends an RRC Connection Setup Complete message to the eNB.
  • Step 1010 The eNB sends an Initial Context Setup Complete message to the MME.
  • the eNB may also be in the RRC Connection in step 1005.
  • the content of the AS Security Mode Command message is carried in the Setup message.
  • the UE may further carry the content of the AS Security Mode Complete message in the RRC Connection Setup Complete message.
  • the RRC Connection Setup message may also include the internal subscription configuration sequence number in step 1005.
  • step 1008 the UE starts the access network subscription configuration information corresponding to the internal subscription configuration sequence number, if the RRC Connection Setup message does not include the internal subscription configuration.
  • the serial number in step 1008, the UE initiates the initially selected access network subscription configuration information.
  • FIG. 11 a schematic flowchart of a method for changing an access network subscription configuration information of an MTC device in an LTE system according to an embodiment of the present application
  • Step 1101 The UE sends an RRC Connection Request message including an S-TMSI to the eNB.
  • Step 1102 The eNB sends an access network subscription configuration query message including an S-TMSI to the MME.
  • Step 1103 After determining that the UE has the update flag, the MME determines, according to the S-TMSI and the internal subscription configuration sequence number, the access network subscription configuration number corresponding to the UE that needs to be updated, and returns an access network subscription configuration number and a change indication to the eNB.
  • Initial Context Setup Request message After determining that the UE has the update flag, the MME determines, according to the S-TMSI and the internal subscription configuration sequence number, the access network subscription configuration number corresponding to the UE that needs to be updated, and returns an access network subscription configuration number and a change indication to the eNB.
  • Step 1104 The eNB searches for the corresponding access network subscription configuration information according to the access network subscription configuration number, and establishes a context for the UE according to the access network subscription configuration information.
  • Step 1105 The eNB sends an RRC Connection Setup message to the UE.
  • step 1006 the eNB sends an AS Security Mode Command message to the UE.
  • step 1007 the UE returns an AS Security Mode Complete message to the eNB.
  • Step 1108 The eNB enables the access network subscription configuration information, and the UE updates the received access network subscription configuration information and the corresponding internal subscription configuration sequence number, and starts the received access network subscription configuration information.
  • Step 1109 The UE sends an RRC Connection Setup Complete message to the eNB.
  • Step 1110 The eNB sends an Initial Context Setup Complete message to the MME.
  • Step 1111 The MME clears the update flag of the UE.
  • the eNB may further carry the content of the AS Security Mode Command message in the RRC Connection Setup message in step 1105; correspondingly, in step 1109, the UE may also be in the RRC Connection Setup Complete message. The content of the AS Security Mode Complete message is carried.
  • the RRC Connection Request message contains the internal subscription configuration sequence number; in step 1003, the Initial Context Setup Request message includes the connection that needs to be updated.
  • the access network subscription configuration information that needs to be updated is the access network subscription configuration information corresponding to the internal subscription configuration sequence number sent by the UE.
  • the method for obtaining the access network subscription configuration information by using the MTC device with only one access network subscription configuration information in the UMTS system includes the following steps:
  • Step 1201 The UE sends an RRC Connection Request message including the P-TMSI to the RNC.
  • Step 1203 The UE sends an RRC Connection Setup Complete message to the RNC.
  • Step 1204 The UE sends a NAS Attach Request message to the RNC.
  • Step 1205 The RNC sends a NAS Attach Request message including a P-TMSI to the SGSN.
  • Step 1206 After determining that the UE is a subscription user of the M2M, the SGSN determines an access network subscription configuration number corresponding to the UE.
  • Step 1207 The SGSN authenticates the UE by using the RNC.
  • Step 1208 The SGSN performs NAS Security Mode Control on the UE through the RNC.
  • Step 1209 The SGSN sends a NAS Attach Accept message to the RNC.
  • Step 1210 The RNC sends a NAS Attach Accept message to the UE.
  • Step 1211 The UE sends a NAS Attach Complete message to the RNC.
  • Step 1212 The RNC sends a NAS Attach Complete message to the SGSN.
  • Step 1213 The UE sends a NAS Active PDP Context Request (non-access stratum active packet protocol context request) message to the RNC.
  • NAS Active PDP Context Request non-access stratum active packet protocol context request
  • Step 1214 The RNC sends a NAS Active PDP Context Request message to the SGSN.
  • Step 1215 The SGSN sends an RAB Assignment including an access network subscription configuration number and a configuration indication to the RNC.
  • Radio Access Bearer Assignment Request (Radio Access Bearer Assignment Request) message
  • Step 1216 The RNC searches for the corresponding access network subscription configuration information according to the access network subscription configuration number.
  • Step 1217 The RNC sends a Radio Bearer Setup message including the access network subscription configuration information to the UE.
  • Step 1218 The UE stores the received access network subscription configuration information.
  • Step 1219 The UE sends a Radio Bearer Setup Complete message to the RNC.
  • Step 1220 The RNC sends an RAB Assignment Response message including configuration confirmation information to the SGSN.
  • Step 1222 The RNC sends a NAS Active PDP Context Accept message to the UE.
  • the method for establishing a connection by using an access network subscription configuration information by an MTC device having only one set of access network subscription configuration information in the UMTS system of the present application includes the following steps: Step 1301: The UE sends an RRC including the establishment cause to the M2M subscription service and the P-TMSI to the RNC.
  • Step 1302 The RNC sends an access network subscription configuration query message including a P-TMSI to the SGSN.
  • Step 1303 The SGSN determines, according to the P-TMSI, the access network subscription configuration number corresponding to the UE, and returns an RAB Assignment Request message including the access network subscription configuration number to the eNB.
  • Step 1304 The RNC searches for the corresponding access network subscription configuration information according to the access network subscription configuration number.
  • Step 1305 The RNC sends an RRC Connection Setup message to the UE.
  • Step 1306 The UE and the RNC enable the access network subscription configuration information.
  • Step 1307 The UE sends an RRC Connection Setup Complete message to the RNC.
  • Step 1308 The RNC sends an RAB Assignment Response message including configuration confirmation information to the SGSN.
  • Step 1310 The RNC sends an RRC Security Mode Command message to the UE.
  • Step 1311 The UE sends an RRC Security Mode Copmlete message to the RNC.
  • Step 1312 The RNC sends a Ranap Security Mode Copmlete message to the SGSN.
  • Step 1313 The UE sends a NAS Active PDP Context Request message to the RNC.
  • Step 1314 The RNC sends a NAS Active PDP Context Request message to the SGSN.
  • Step 1315 The SGSN sends a NAS Active PDP Context Accept message to the RNC.
  • Step 1316 The RNC sends a NAS Active PDP Context Accept message to the UE.
  • the method for changing the access network subscription configuration information of the MTC device with only one set of access network subscription configuration information in the UMTS system includes the following steps:
  • Step 1401 The UE sends an RRC to the RNC that includes the establishment cause M2M subscription service and P-TMSI.
  • Step 1402 The RNC sends an access network subscription configuration query message including the P-TMSI to the SGSN.
  • Step 1403 The SGSN determines that the UE has an update flag, determines an access network subscription configuration number that the UE needs to update according to the P-TMSI, and returns an RAB that includes an access network subscription configuration number and an update indication to the eNB.
  • Step 1404 The RNC searches for the corresponding access network subscription configuration information according to the access network subscription configuration number.
  • Step 1405 The RNC sends an RRC Connection Setup message including the access network subscription configuration information to the UE.
  • Step 1406 The RNC enables the access network subscription information.
  • the configuration information is updated by the UE according to the received access network subscription configuration information, and the received access network subscription configuration information is started;
  • Step 1407 The UE sends an RRC Connection Setup Complete message to the RNC.
  • Step 1408 The RNC sends a RAB Assignment Response message including the update confirmation information to the SGSN.
  • Step 1410 The SGSN sends a Ranap Security Mode Command message to the RNC.
  • Step 1411 The RNC sends an RRC Security Mode Command message to the UE.
  • Step 1412 The UE sends an RRC Security Mode Copmlete message to the RNC.
  • Step 1413 The RNC sends a Ranap Security Mode Copmlete message to the SGSN.
  • Step 1414 The UE sends a NAS Active PDP Context Request message to the RNC.
  • Step 1415 The RNC sends a NAS Active PDP Context Request message to the SGSN.
  • Step 1416 The SGSN sends a NAS Active PDP Context Accept message to the RNC.
  • Step 1417 The RNC sends a NAS Active PDP Context Accept message to the UE.
  • the method for obtaining the access network subscription configuration information by using the MTC device with multiple access network subscription configuration information in the UMTS system includes the following steps:
  • Step 1501 The UE sends an RRC Connection Request message including the P-TMSI to the RNC.
  • Step 1503 The UE sends an RRC Connection Setup Complete message to the RNC.
  • Step 1504 The UE sends a NAS Attach Request message to the RNC.
  • Step 1505 The RNC sends a NAS Attach Request message including a P-TMSI to the SGSN.
  • Step 1506 After determining that the UE is a subscription user of the M2M, the SGSN determines an access network subscription configuration number and an internal subscription configuration sequence number corresponding to the UE.
  • Step 1507 The SGSN authenticates the UE by using the RNC.
  • Step 1508 The SGSN performs NAS Security Mode Control on the UE through the RNC.
  • Step 1509 The SGSN sends a NAS Attach Accept message to the RNC.
  • Step 1510 The RNC sends a NAS Attach Accept message to the UE.
  • Step 1511 The UE sends a NAS Attach Complete message to the RNC.
  • Step 1512 The RNC sends a NAS Attach Complete message to the SGSN.
  • Step 1513 The UE sends a NAS Active PDP Context Request message to the RNC.
  • Step 1514 The RNC sends a NAS Active PDP Context Request message to the SGSN.
  • Step 1515 The SGSN sends an RAB Assignment Request message including an access network subscription configuration number, an internal subscription configuration sequence number, and a configuration indication to the RNC.
  • Step 1516 The RNC searches for the corresponding access network subscription configuration information according to the access network subscription configuration number.
  • Step 1517 The RNC sends the radio, including the access network subscription configuration information and the internal subscription configuration serial number, to the UE.
  • Step 1518 The UE establishes and stores a correspondence between the received access network subscription configuration information and the internal subscription configuration sequence number.
  • Step 1519 The UE sends a Radio Bearer Setup Complete message to the RNC.
  • Step 1520 The RNC sends an RAB Assignment Response message including the configuration confirmation information to the SGSN.
  • Step 1522 The RNC sends a NAS Active PDP Context Accept message to the UE.
  • the method for establishing a connection by using an access network subscription configuration information by an MTC device having multiple sets of access network subscription configuration information in the UMTS system includes the following steps:
  • Step 1601 The UE sends an RRC Connection Request message to the RNC that includes an internal subscription configuration sequence number corresponding to the M2M subscription service, the P-TMSI, and the access network configuration information that needs to be enabled.
  • Step 1602 The RNC sends an access network subscription configuration query message including the P-TMSI and the internal subscription configuration sequence number to the SGSN.
  • Step 1603 The SGSN determines, according to the P-TMSI and the internal subscription configuration sequence number, the access network subscription configuration number corresponding to the UE, and returns an RAB Assignment Request message including the access network subscription configuration number to the eNB.
  • Step 1604 The RNC searches for the corresponding access network subscription configuration information according to the access network subscription configuration number.
  • Step 1605 The RNC sends an RRC Connection Setup message to the UE.
  • Step 1606 The RNC enables the access network subscription configuration information, and the UE enables the access network subscription configuration information corresponding to the internal subscription configuration sequence number.
  • Step 1607 The UE sends an RRC Connection Setup Complete message to the RNC.
  • Step 1608 The RNC sends an RAB Assignment Response message including configuration confirmation information to the SGSN.
  • Step 1609 The SGSN sends a Ranap Security Mode Command message to the RNC.
  • Step 1610 The RNC sends an RRC Security Mode Command message to the UE.
  • Step 1611 The UE sends an RRC Security Mode Copmlete message to the RNC.
  • Step 1612 The RNC sends a Ranap Security Mode Copmlete message to the SGSN.
  • Step 1613 The UE sends a NAS Active PDP Context Request message to the RNC.
  • Step 1614 The RNC sends a NAS Active PDP Context Request message to the SGSN.
  • Step 1615 The SGSN sends a NAS Active PDP Context Accept message to the RNC.
  • Step 1616 The RNC sends a NAS Active PDP Context Accept message to the UE.
  • the RAB Assignment Request message may further include an internal subscription configuration sequence number.
  • the RRC Connection Setup message further includes an internal subscription configuration sequence number.
  • the UE enables the internal subscription configuration sequence number. Corresponding access network configuration information,
  • the method for changing the access network subscription configuration information of the MTC device in the UMTS system with multiple sets of access network subscription configuration information includes the following steps:
  • Step 1701 The UE sends, to the RNC, an RRC Connection Request message that includes an internal subscription configuration sequence number corresponding to the M2M subscription service, the P-TMSI, and the access network configuration information that needs to be enabled.
  • Step 1702 The RNC sends an access network subscription configuration query message including the P-TMSI and the internal subscription configuration sequence number to the SGSN.
  • Step 1703 The SGSN determines that the UE has an update flag, and determines, according to the P-TMSI and the internal subscription configuration sequence number, an access network subscription configuration number corresponding to the UE that needs to be updated, and returns an access network subscription configuration number to the eNB, and needs to be updated.
  • the internal subscription configuration sequence corresponding to the access network subscription configuration information that needs to be updated is the same as the internal subscription configuration sequence received by the SGSN.
  • Step 1704 The RNC searches for the corresponding access network subscription configuration information according to the access network subscription configuration number.
  • Step 1705 The RNC sends an RRC Connection Setup message including the internal subscription configuration sequence number and the access network subscription configuration information to the UE.
  • Step 1706 The RNC enables the access network subscription configuration information, and the UE updates the received access network subscription configuration information and the corresponding internal subscription configuration sequence number, and starts the received access network subscription configuration information.
  • Step 1707 The UE sends an RRC Connection Setup Complete message to the RNC.
  • Step 1708 The RNC sends an RAB Assignment Response message including the update confirmation information to the SGSN.
  • Step 1709 The SGSN clears the update flag to the UE.
  • Step 1710 The SGSN sends a Ranap Security Mode Command message to the RNC.
  • Step 1711 The RNC sends an RRC Security Mode Command message to the UE.
  • Step 1712 The UE sends an RRC Security Mode Copmlete message to the RNC.
  • Step 1713 The RNC sends a Ranap Security Mode Copmlete message to the SGSN.
  • Step 1714 The UE sends a NAS Active PDP Context Request message to the RNC.
  • Step 1715 The RNC sends a NAS Active PDP Context Request message to the SGSN.
  • Step 1716 The SGSN sends a NAS Active PDP Context Accept message to the RNC.
  • Step 1717 The RNC sends a NAS Active PDP Context Accept message to the UE.
  • Steps 13 to 16 in Figure 13 and Figure 16 The PDP context activation process, and the steps 14 to 17 in Figure 14 and Figure 17 are all optional.
  • the process is as follows:
  • Scenario 1 The network side performs the Iu Release Request process (the reason is User Inactivity), the PDP context is reserved, and the RAB is released.
  • the MTC device uses the access network subscription configuration to establish the connection process. Steps 13 to 13 in FIG. 13 and FIG.
  • the PDP context activation process does not occur, and the PDP context activation process does not appear in steps 14 to 17 in FIG. 14 and FIG. 17 corresponding to the process of changing the MTC device access network subscription configuration number;
  • Scenario 2 The network side performs the PDP deactivation process, the PDP context is deactivated, and the RAB is released. Then the MTC is set. The PDP context activation process must be performed in steps 13 to 16 in FIG. 13 and FIG. 16 for the connection establishment process to establish the connection process.
  • the process of changing the MTC Device access network subscription configuration number process corresponds to FIG. 14 and FIG. Steps 14 to 17
  • the PDP context activation process must appear.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the application can be in the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware.
  • the application can be in the form of a computer program product embodied on one or more computer-usable storage interfaces (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本发明涉及无线通信技术领域，特别涉及一种建立连接的方法、系统和设备。本发明的方法包括：接入网设备通过核心网设备确定发起连接请求的机器类型（MTC）设备对应的接入网签约配置编号（501）；接入网设备根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系，确定所述MTC设备的接入网签约配置编号对应的接入网签约配置信息（502）；所述接入网设备根据确定的接入网签约配置信息与所述MTC设备建立连接（503）。本发明的接入网能够根据MTC设备对应的接入网签约配置信息与该MTC设备建立连接，从而减少连接建立过程中的信令开销，进而提高系统效率。

Description

一种建立连接的方法、 系统和设备 本申请要求在 2011年 10月 18日提交中国专利局、 申请号为 201110317217.1、 发明名称为
"一种建立连接的方法、 系统和设备"的中国专利申请的优先权， 其全部内容通过引用结合在本 申请中。 技术领域 本申请涉及无线通信技术领域， 特别涉及一种建立连接的方法、 系统和设备。 背景技术 为了便于新业务的开展， LTE ( Long Term Evolution, 长期演进）系统釆用了用户面与 控制面分离的设计方式， 控制面信令与用户面承载分别由独立的网元 MME ( Mobile Management Entity, 移动管理实体）和 S-GW ( Serving GW, 服务网关）来负责。 MME主 要功能是 NAS ( Non Access Stratum, 非接入层）信令建立、 NAS信令安全、 跨核心网的 信令建立、 跟踪服务、 漫游服务、 授权和承载管理等。 S-GW为 e B (演进基站）切换时 的关口点、 转发 2G / 3G以及其他系统业务的关口点， 完成下行包的緩冲、 一些初始化工 作、 规定的拦截侦听、 包路由和转发等。 P-GW ( PDN GW, 分组数据网关）用于策略的执 行、 包过滤、 规定的拦截、 地址的分配、 计费功能、 包再现等。
UE (用户设备）、 eNB与核心网之间的控制信令通过 MME进行处理； 用户数据通过 S-GW传输到 P-GW, 然后由 P-GW传输到外部的各类 APN ( Access Point Name, 接入点 名） 节点。 由于减少了控制信令与用户数据的耦合， 当新业务出现只需对负责用户面承载 的网元进行升级， 而不会对控制信息传输造成影响， 从而极大地降低了网络维护的复杂度 和设备升级成本。
MTC ( Machine-type communication, 机器类型）通信作为一种新型的通信理念， 其目 的是将多种不同类型的通信技术有机结合， 如： 机器对机器通信、 机器控制通信、 人机交 互通信、 移动互联通信， 从而推动社会生产和生活方式的发展。 预计未来人对人通信的业 务可能仅占整个终端市场的 1/3 , 而更大数量的通信是 MTC通信业务。 有时， MTC通信 又称为 M2M ( Machine-to-machine, 机器间）通信或物联网。
当前的移动通信网络是针对人与人之间的通信设计的， 如： 网络容量的确定等。 如果 希望利用移动通信网络来支持 MTC通信就需要根据 MTC通信的特点对移动通信系统的机 制进行优化， 以便能够在对传统的人与人通信不受或受较小影响的情况下， 更好地实现 MTC通信。 目前， 网络需要为每个 MTC设备进行复杂的信令流程建立 DRB (数据无线承载） /RB (无线承载）、 SI ( e B与 MME之间的接口 ) /Iu ( RNC与核心网之间的接口 )承载后， 才能通过 DRB/RB、 Sl/Iu承载将数据发送给网络侧， 这样就会造成信令开销比较大， 从而 降低了系统效率。 发明内容 本申请实施例提供一种建立连接的方法、 系统和设备 , 用以减少向网络侧发送数据之 前的建立过程中的信令开销， 从而提高系统效率。
本申请实施例提供的一种建立连接的方法， 包括：
接入网设备通过核心网设备确定发起连接请求的机器类型 MTC设备的接入网签约配 置编号；
接入网设备根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系， 确定所述 MTC设备的接入网签约配置编号对应的接入网签约配置信息；
所述接入网设备根据确定的接入网签约配置信息与所述 MTC设备建立连接。
本申请实施例提供的另一种建立连接的方法， 包括：
核心网设备确定向接入网设备发起连接请求的 MTC设备的接入网签约配置编号； 所述核心网设备向所述接入网设备发送所述接入网签约配置编号， 用于通知所述接入 网设备根据所述接入网签约配置编号对应的接入网签约配置信息与所述 MTC设备建立连 接。
本申请实施例提供的另一种建立连接的方法， 包括：
MTC设备向接入网设备发起连接请求；
所述 MTC设备根据对应的接入网签约配置信息与所述接入网设备建立连接。
本申请实施例提供的一种建立连接的接入网设备， 包括：
确定模块， 用于通过核心网设备确定发起连接请求的 MTC设备的接入网签约配置编 号， 根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系， 确定所述 MTC设备的接入网签约配置编号对应的接入网签约配置信息；
第一建立模块， 用于根据确定的接入网签约配置信息与所述 MTC设备建立连接。 本申请实施例提供的一种建立连接的核心网设备， 包括：
处理模块， 用于确定向接入网设备发起连接请求的 MTC设备的接入网签约配置编号； 发送模块， 用于向所述接入网设备发送所述接入网签约配置编号， 用于通知所述接入 网设备根据所述接入网签约配置编号对应的接入网签约配置信息与所述 MTC设备建立连 接。 本申请实施例提供的一种建立连接的 MTC设备， 包括：
上 莫块， 向接入网设备发起连接请求；
第二建立模块， 用于根据对应的接入网签约配置信息与所述接入网设备建立连接。 本申请实施例提供的一种建立连接的系统， 包括：
接入网设备 , 用于通过核心网设备确定发起连接请求的 MTC设备的接入网签约配置 编号， 根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系， 确定所述 MTC设备的接入网签约配置编号对应的接入网签约配置信息，根据确定的接入网签约配置 信息与所述 MTC设备建立连接。
核心网设备， 用于确定向接入网设备发起连接请求的 MTC设备的接入网签约配置编 号， 向所述接入网设备发送所述接入网签约配置编号；
MTC设备，用于向接入网设备发起连接请求，根据对应的接入网签约配置信息与所述 接入网设备建立连接。
由于在 MTC的应用场景中， 业务特性完全相同， 可以使用相同的接入网签约配置信 息，本申请实施例接入网能够根据 MTC设备对应的接入网签约配置信息与该 MTC设备建 立连接， 从而减少向网络侧发送数据之前的建立过程中的信令开销， 从而提高系统效率。 附图说明 图 1为本申请实施例建立连接的系统结构示意图；
图 2为本申请实施例接入网设备的结构示意图；
图 3为本申请实施例核心网设备的结构示意图；
图 4为本申请实施例 MTC设备的结构示意图；
图 5为本申请实施例接入网设备侧进行建立连接的方法流程示意图；
图 6为本申请实施例核心网设备侧通知进行建立连接的方法流程示意图；
图 7为本申请实施例 MTC设备侧进行建立连接的方法流程示意图；
图 8为本申请实施例在 LTE系统中， MTC设备通过信令获取接入网签约配置信息的 方法流程示意图；
图 9为本申请实施例在 LTE系统中， 只有一套接入网签约配置信息的 MTC设备使用 接入网签约配置信息建立连接的方法流程示意图；
图 10为本申请实施例在 LTE系统中，有多套接入网签约配置信息的 MTC设备使用接 入网签约配置信息建立连接的方法流程示意图；
图 11为本申请实施例在 LTE系统中， 变更 MTC设备的接入网签约配置信息的方法 流程示意图； 图 12为本申请实施例在 UMTS中，只能一套接入网签约配置信息的 MTC设备通过信 令获取接入网签约配置信息的方法流程示意图；
图 13为本申请实施例在 UMTS中，只有一套接入网签约配置信息的 MTC设备使用接 入网签约配置信息建立连接的方法流程示意图；
图 14为本申请实施例在 UMTS中， 只有一套接入网签约配置信息变更 MTC设备的 接入网签约配置信息的方法流程示意图；
图 15为本申请实施例在 UMTS中，有多套接入网签约配置信息的 MTC设备通过信令 获取接入网签约配置信息的方法流程示意图；
图 16为本申请实施例在 UMTS中，系统有多套接入网签约配置信息的 MTC设备使用 接入网签约配置信息建立连接的方法流程示意图；
图 17为本申请实施例在 UMTS中，系统有多套接入网签约配置信息变更 MTC设备的接 入网签约配置信息的方法流程示意图。 具体实施方式 针对网络需要为每个 MTC设备进行复杂的信令流程建立 DRB/RB、 Sl/Iu承载后， 才 能通过 DRB/RB、 Sl/Iu承载将数据发送给网络侧， 这样就会造成信令开销比较大， 从而降 低了系统效率的问题。 本申请实施例 MTC USER与网络运营商协商确定 MTC设备使用的 接入网签约配置，并将每个 MTC设备使用的接入网签约配置编号存储在核心网中，当 MTC 设备发起连接请求时， 接入网向核心网查询该 MTC设备的接入网签约配置编号， 接入网 依据该接入网签约配置编号在本地查询确定对应的接入网签约配置信息， 并使用该接入网 签约配置信息为该 MTC设备建立连接。 由于在 MTC的应用场景中， 业务特性完全相同， 可以使用相同的接入网签约配置信息， 本申请实施例接入网能够根据 MTC设备对应的接 入网签约配置信息与该 MTC设备建立连接， 也就是说， 通过接入网签约配置的方式筒化 了 RRC建立消息， 且在 RRC建立过程中就同时建立业务承载， 从而省略了之后建立业务 承载的过程， 减少向网络侧发送数据之前的建立过程中的信令开销， 从而提高系统效率。
其中， 本申请实施例的接入网签约配置信息包括但不限于下列信息中的至少一种： SRB ( Signaling Radio Bearer, 信令无线承载）信息、 DRB ( Data Radio Bearer, 数据 无线承载）信息、 RB ( Radio Bearer, 无线承载）信息、 PDCP ( Packet Data Convergence Protocol, 分组数据聚合协议）信息、 RLC ( Radio Link Control, 无线链路控制）信息、 MAC ( Medium Access Control; 媒体接入控制 )信息和物理层的配置参数（ antennalnfo , tpc, transmissionMode (传输模式， 比如 LTE传输模式）等）。
由于使用签约配置的 MTC设备在每次发起连接建立的时候可以直接使用预先存储的 签约配置参数， 减少了 RRC连接重配置信令过程（LTE )和 RB建立过程 ( UMTS ) 的信 令数量， 从而降低了信令负荷。
其中， 本申请实施例的方案可以应用于 LTE 系统和 UMTS ( Universal Mobile TelecommunicationSystem , 通用移动通信系统）， 还可以应用于其他需要 MTC设备与接入 网设备建立连接的系统。
在下面的说明过程中， 先从网络侧和终端侧的配合实施进行说明， 最后分别从网络侧 与终端侧的实施进行说明， 但这并不意味着二者必须配合实施， 实际上， 当网络侧与终端 侧分开实施时， 也解决了分别在网络侧、 终端侧所存在的问题， 只是二者结合使用时， 会 获得更好的技术效果。
如图 1所示， 本申请实施例建立连接的系统包括： 接入网设备 10、 核心网设备 20和
MTC设备 30。
接入网设备 10, 用于通过核心网设备 20确定发起连接请求的 MTC设备 30的接入网 签约配置编号， 根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系， 确定 MTC设备 30的接入网签约配置编号对应的接入网签约配置信息，根据确定的接入网 签约配置信息与 MTC设备 30建立连接。
核心网设备 20, 用于确定向接入网设备 10发起连接请求的 MTC设备 30的接入网签 约配置编号， 向接入网设备 10发送接入网签约配置编号；
MTC设备 30, 用于向接入网设备 10发起连接请求， 根据对应的接入网签约配置信息 与接入网设备 10建立连接。
其中，根据 MTC设备 30的性能不同，有的 MTC设备 30对应一个接入网签约配置信 息， 有的 MTC设备 30对应多个接入网签约配置信息， 下面分别进行介绍。
情况一、 MTC设备 30对应一个接入网签约配置信息。
较佳地， MTC设备 30在需要发起连接时， 向接入网设备发起包含 MTC设备 30的设 备标识的连接请求；
相应的， 接入网设备 10将收到的连接请求中的设备标识发送给核心网设备 20;
核心网设备 20根据预先设定的设备标识和接入网签约配置编号的对应关系， 确定 MTC设备 30的设备标识对应的接入网签约配置编号， 并返回给接入网设备 10;
接入网设备 10根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关 系， 确定 MTC设备 30的接入网签约配置编号对应的接入网签约配置信息， 并通知 MTC 设备 30启动接入网签约配置信息。
较佳地， 核心网设备 20在收到设备标识后， 首先需要判断对应的 MTC设备 30是否 是签约用户设备（比如 Μ2Μ签约用户设备）， 如果是， 再进一步确定对应的接入网签约配 置编号； 如果不是签约用户， 按照现有核心网协议 23.401 ( LTE核心网）和 23.060 ( UMTS 核心网）规定的流程进行。
核心网不会下发签约配置编号，这样接入网就不会下发全部签约配置内容。对于 MTC 设备 30使用接入网签约配置建立连接的过程， MTC设备 30发起 RRC连接建立， 签约用 户使用的建立原因是 M2M签约用户， 而非签约用户不使用这个原因， 因此接入网能区分 开来。
其中， MTC设备 30的设备标识是可以唯一标识一个 MTC设备的信息， 包括但不限 于下列信息中的一种：
IMSI ( International Mobile Subscriber Identity, 国际移动用户标识码）、 P-TMSI ( Packet - Temporary Mobile Subscriber Identify, 分组临时移动用户识别号码）、 S-TMSI ( SAE - Temporary Mobile Subscriber Identify, SAE 临时移动用户识别号码）和 GUTI ( Globally Unique Temporary Identify, 全 ί求唯一临时标 i只)等。
若 MTC设备 30发送的是 P-TMSI或 S-TMSI或 GUTI,则核心网设备 20根据 P-TMSI 或 S-TMSI或 GUTI可以确定对应的 IMSI。
如果本申请实施例应用于 LTE 系统中， 则核心网中存储签约配置编号的设备可以是 MME( Mobility Management Entity,移动性管理实体）， S-GW, P-GW, HSS( Home Subscriber Server, 归属签约用户服务器）， 中间节点等；
如果本申请实施例应用于 UMTS 中， 则核心网中存储签约配置编号的设备可以是 SGSN ( Serving GPRS Support Node,服务 GPRS支持节点）， HLR ( Home Location Register, 归属位置寄存器）， 中间节点等。
对于接入网签约配置信息， 可以有三种方式：
方式一、 MTC设备 30在出厂前就将接入网签约配置信息直接存储在设备里， 即 MTC 设备 30预先存储接入网签约配置信息。
方式二、 MTC设备 30未预先存储接入网签约配置信息， 由网络侧通过系统消息广播， 即 MTC设备 30首次接入时， 网络通知 MTC设备 30签约配置编号， MTC设备 30读取广 播中的对应接入网签约配置信息， 进行存储。
较佳地，核心网设备 20在确定向接入网设备 10发起连接请求的 MTC设备 30未存储 接入网签约配置信息， 且 MTC设备 30对应一个接入网签约配置信息后， 根据预先设定的 设备标识和接入网签约配置编号的对应关系，确定 MTC设备 30的设备标识对应的接入网 签约配置编号， 并向接入网设备 10发送确定的接入网签约配置编号；
接入网设备 10根据接入网签约配置编号和接入网签约配置信息的对应关系， 确定收 到的接入网签约配置编号对应的接入网签约配置信息， 通过广播发送所有的接入网签约配 置信息， 并通过 RRC信令通知 MTC设备所有的接入网签约配置信息中属于该 MTC设备 的接入网签约配置信息； MTC设备 30存储接入网设备通知的 MTC设备对应的接入网签约配置信息。
方式三、 MTC设备 30未预先存储接入网签约配置信息， MTC设备 30首次接入时， 由网络将接入网签约配置的完整信息通过信令传给 MTC设备。 网络可以通过信令变更接 入网签约配置的信息。
具体的，核心网设备 20在确定向接入网设备 10发起连接请求的 MTC设备 30未存储 接入网签约配置信息， 且 MTC设备 30对应一个接入网签约配置信息后， 根据预先设定的 设备标识和接入网签约配置编号的对应关系，确定 MTC设备 30的设备标识对应的接入网 签约配置编号， 并向接入网设备 10发送确定的接入网签约配置编号；
接入网设备 10根据接入网签约配置编号和接入网签约配置信息的对应关系， 确定收 到的接入网签约配置编号对应的接入网签约配置信息，通过 RRC信令通知 MTC设备对应 的接入网签约配置信息；
MTC设备 30存储接入网设备 10通知的 MTC设备对应的接入网签约配置信息。 情况一中，根据需要还可以对接入网签约配置信息进行更新，下面列举两种更新方式。 方式一、核心网设备 20判断 MTC设备是否有更新标记， 如果 MTC设备有更新标记， 则通知接入网设备 10需要为 MTC设备 30进行更新的接入网签约配置信息对应的接入网 签约配置编号；
接入网设备 10在收到需要进行更新的接入网签约配置信息对应的接入网签约配置编 号后， 就确定 MTC设备 30有更新标记， 然后根据接入网签约配置编号和接入网签约配置 信息的对应关系， 确定收到的接入网签约配置编号对应的接入网签约配置信息， 并向需要 进行接入网签约配置信息更新的 MTC设备 30发起寻呼通知 MTC设备读取系统消息， 以 及发送包含更新的接入网签约配置信息的系统消息；
MTC设备 30根据收到的来自接入网设备 10的需要进行更新的接入网签约配置信息， 更新存储的接入网签约配置信息。
方式二、核心网设备 20判断 MTC设备是否有更新标记， 如果 MTC设备有更新标记， 则通知接入网设备 10需要为 MTC设备 30进行更新的接入网签约配置信息对应的接入网 签约配置编号；
接入网设备 10在收到需要进行更新的接入网签约配置信息对应的接入网签约配置编 号后， 就确定 MTC设备 30有更新标记， 然后根据接入网签约配置编号和接入网签约配置 信息的对应关系，确定收到的接入网签约配置编号对应的接入网签约配置信息， 并在 MTC 设备 30发起业务请求时， 通过发送包含更新的接入网签约配置信息的专用信令通知 MTC 设备 30更新对应的接入网签约配置信息；
MTC设备 30根据收到的来自接入网设备 10的需要进行更新的接入网签约配置信息， 更新存储的接入网签约配置信息。 较佳地， 接入网设备 10在确定 MTC设备 30的更新完成后 （比如收到 MTC设备 30 返回的确认消息）， 通知核心网设备去除 MTC设备的更新标记； 核心网设备 20去除 MTC 设备的更新标记。
情况二、 MTC设备 30对应多个接入网签约配置信息。
较佳地， MTC设备 30向接入网设备 10发起包含 MTC设备 30的设备标识和建立连 接需要使用的接入网签约配置信息对应的内部签约配置序列号的连接请求；
相应的， 接入网设备 10将收到的连接请求中的设备标识和内部签约配置序列号发送 给核心网设备 20;
核心网设备 20根据预先设定的设备标识、 内部签约配置序列号和接入网签约配置编 号的对应关系，确定 MTC设备 30的设备标识和内部签约配置序列号对应的接入网签约配 置编号， 并返回给接入网设备 10;
接入网设备 10根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关 系， 确定 MTC设备 30的接入网签约配置编号对应的接入网签约配置信息， 并将从核心网 设备获取的 MTC设备对应的内部签约配置序列号发送给 MTC设备 , 用于通知 MTC设备 启动内部签约配置序列号对应的接入网签约配置信息。
较佳地， 核心网设备 20在收到设备标识后， 首先需要判断对应的 MTC设备 30是否 是签约用户设备（比如 M2M签约用户设备）， 如果是， 再进一步确定对应的接入网签约配 置编号； 如果不是， 则按照现有核心网协议 23.401 ( LTE核心网）和 23.060 ( UMTS核心 网）规定的流程进行。
其中， MTC设备 30的设备标识是可以唯一标识一个 MTC设备的信息， 包括但不限 于下列信息中的一种：
IMSI、 P-TMSI、 S-TMSI和 GUTI。
若 MTC设备 30发送的是 P-TMSI或 S-TMSI或 GUTI,则核心网设备 20根据 P-TMSI 或 S-TMSI或 GUTI可以确定对应的 IMSI。
如果本申请实施例应用于 LTE 系统中， 则核心网中存储签约配置编号的设备可以是
MME, S-GW, P-GW, HSS, 中间节点等；
如果本申请实施例应用于 UMTS 中， 则核心网中存储签约配置编号的设备可以是 SGSN, HLR, 中间节点等。
对于接入网签约配置信息， 可以有三种方式：
方式一、 MTC设备 30在出厂前就将接入网签约配置信息直接存储在设备里， 即 MTC 设备 30预先存储接入网签约配置信息。
方式二、 MTC设备 30未预先存储接入网签约配置信息， 由网络侧通过系统消息广播， 即 MTC设备 30首次接入时， 网络通知 MTC设备 30签约配置编号， MTC设备 30读取广 播中的对应接入网签约配置信息， 进行存储。
较佳地，核心网设备 20在确定向接入网设备 10发起连接请求的 MTC设备 30未存储 接入网签约配置信息， 且 MTC设备 30对应多个接入网签约配置信息后， 根据预先设定的 设备标识和接入网签约配置编号的对应关系，确定 MTC设备 30的设备标识对应的所有接 入网签约配置编号， 并向接入网设备 10发送确定的所有接入网签约配置编号；
接入网设备 10根据接入网签约配置编号和接入网签约配置信息的对应关系， 确定收 到的每个接入网签约配置编号对应的接入网签约配置信息， 通过广播发送所有的接入网签 约配置信息， 并通过 RRC信令通知 MTC设备所有的接入网签约配置信息中属于该 MTC 设备的接入网签约配置信息；
MTC设备 30根据接入网设备通知的 MTC设备对应的接入网签约配置信息， 以及每 个接入网签约配置信息的顺序， 建立并存储接入网签约配置信息和内部签约配置序列号的 对应关系。
比如有 10个接入网签约配置信息， MTC设备 30确定对应的三个接入网签约配置信息 是 5、 8和 9, 则确定第 5个接入网签约配置信息对应的内部签约配置序列号是 0、 确定第 8个接入网签约配置信息对应的内部签约配置序列号是 1 , 确定第 9个接入网签约配置信 息对应的内部签约配置序列号是 2。
除了上面的按照顺序确定内部签约配置序列号的方式， 还可以直接将内部签约配置序 列号通知给 MTC设备 30。
具体的， 核心网设备 20根据预先设定的设备标识、 内部签约配置序列号和接入网签 约配置编号的对应关系，确定 MTC设备 30的设备标识对应的所有的内部签约配置序列号 和接入网签约配置编号， 并向接入网设备 10发送确定的内部签约配置序列号和对应的接 入网签约配置编号；
相应的， 接入网设备 10将所有接入网签约配置编号对应的接入网签约配置信息和来 自核心网设备 20的针对 MTC设备 30的接入网签约配置信息对应的内部签约配置序列号 通过广播发送给 MTC设备 30;
MTC设备 30根据收到的接入网签约配置信息和对应的内部签约配置序列号， 建立并 存储接入网签约配置信息和内部签约配置序列号的对应关系。
方式三、 MTC设备 30未预先存储接入网签约配置信息， MTC设备 30首次接入时， 由网络将接入网签约配置的完整信息通过信令传给 MTC设备。 网络可以通过信令变更接 入网签约配置的信息。
具体的，核心网设备 20在确定向接入网设备 10发起连接请求的 MTC设备 30未存储 接入网签约配置信息， 且 MTC设备 30对应多个接入网签约配置信息后， 根据预先设定的 设备标识和接入网签约配置编号的对应关系，确定 MTC设备 30的设备标识对应的所有接 入网签约配置编号， 并向接入网设备 10发送确定的接入网签约配置编号；
接入网设备 10根据接入网签约配置编号和接入网签约配置信息的对应关系， 确定收 到的每个接入网签约配置编号对应的接入网签约配置信息，通过 RRC信令通知 MTC设备 对应的所有接入网签约配置信息；
MTC设备 30根据接入网设备 10通知的 MTC设备 30对应的接入网签约配置信息， 以及每个接入网签约配置信息的顺序， 建立并存储接入网签约配置信息和内部签约配置序 列号的对应关系。
比如有 10个接入网签约配置信息， MTC设备 30确定对应的三个接入网签约配置信息 是 5、 8和 9, 则确定第 5个接入网签约配置信息对应的内部签约配置序列号是 0、 确定第 8个接入网签约配置信息对应的内部签约配置序列号是 1 , 确定第 9个接入网签约配置信 息对应的内部签约配置序列号是 2。
除了上面的按照顺序确定内部签约配置序列号的方式， 还可以直接将内部签约配置序 列号通知给 MTC设备 30。
具体的， 核心网设备 20根据预先设定的设备标识、 内部签约配置序列号和接入网签 约配置编号的对应关系，确定 MTC设备 30的设备标识对应的所有内部签约配置序列号和 接入网签约配置编号， 并向接入网设备 10发送确定的内部签约配置序列号和对应的接入 网签约配置编号；
相应的， 接入网设备 10将收到的接入网签约配置编号对应的接入网签约配置信息和 来自核心网设备 20的针对 MTC设备 30的接入网签约配置信息对应的内部签约配置序列 号， 通过 RRC消息发送给 MTC设备 30;
MTC设备 30根据收到的接入网签约配置信息和内部签约配置序列号， 建立并存储接 入网签约配置信息和内部签约配置序列号的对应关系。
情况二中， 根据需要还可以对接入网签约配置信息进行更新， 这里的更新包括替换接 入网签约配置信息和增加接入网签约配置信息。 下面列举两种更新方式。
方式一、核心网设备 20判断 MTC设备是否有更新标记， 如果 MTC设备有更新标记， 则通知接入网设备 10需要为 MTC设备 30进行更新的接入网签约配置信息对应的接入网 签约配置编号和内部签约配置序列号；
接入网设备 10在收到需要进行更新的接入网签约配置信息对应的接入网签约配置编 号后， 就知道 MTC设备 30有更新标记， 然后根据接入网签约配置编号和接入网签约配置 信息的对应关系， 确定收到的接入网签约配置编号对应的接入网签约配置信息， 并向需要 进行接入网签约配置信息更新的 MTC设备 30发起寻呼通知 MTC设备读取系统消息， 以 及发送包含更新的接入网签约配置信息和内部签约配置序列号的系统消息；
MTC设备 30根据收到的接入网签约配置信息和内部签约配置序列号， 更新存储的接 入网签约配置信息和对应的内部签约配置序列号。
方式二、核心网设备 20判断 MTC设备是否有更新标记， 如果 MTC设备有更新标记， 则通知接入网设备 10需要为 MTC设备 30进行更新的接入网签约配置信息对应的接入网 签约配置编号和内部签约配置序列号；
接入网设备 10在收到需要进行更新的接入网签约配置信息对应的接入网签约配置编 号后， 就知道 MTC设备 30有更新标记， 然后根据接入网签约配置编号和接入网签约配置 信息的对应关系，确定收到的接入网签约配置编号对应的接入网签约配置信息， 并在 MTC 设备 30发起业务请求时， 通过发送包含更新的接入网签约配置信息和对应的内部签约配 置序列号的专用信令， 通知 MTC设备 30更新对应的接入网签约配置信息；
MTC设备 30根据收到的接入网签约配置信息和内部签约配置序列号， 更新存储的接 入网签约配置信息和对应的内部签约配置序列号。
较佳地， 接入网设备 10在确定 MTC设备 30的更新完成后 （比如收到 MTC设备 30 返回的确认消息）， 通知核心网设备 20去除 MTC设备 30的更新标记； 核心网设备 20去 除 MTC设备 30的更新标记。
上述情况一和情况二中， 一种较佳地方式是将更新过程和连接过程融合在一起， 即接 入网设备 10在需要对发起连接的 MTC设备 30进行更新时， 可以将需要更新的接入网签 约配置信息置于针对 MTC设备 30连接请求的反馈信息中； 相应的， MTC设备 30若接收 到的反馈信息中没有接入网签约配置信息， 则用初始选择的接入网签约配置信息与接入网 设备 10进行连接； 若接收到的反馈信息中有接入网签约配置信息， 则进行接入网签约配 置信息的更新， 并根据接入网设备的通知用初始选择的接入网签约配置信息或更新后的接 入网签约配置信息与接入网设备进行连接（如果更新的是初始选择的接入网签约配置信 息， 则直接用更新后的接入网签约配置信息与接入网设备进行连接）。
从上述内容可以看出： 如果 MTC设备 30支持多个接入网签约配置信息， 则 MTC设 备 30会建立接入网签约配置信息和内部签约配置序列号的对应关系。 内部签约配置序列 号的作用与接入网签约配置编号的作用相同， 都是用于识别接入网签约配置信息， 只是接 入网签约配置编号的作用是为了接入网设备 10识别接入网签约配置信息； 内部签约配置 序列号的作用是为了 MTC设备 30识别接入网签约配置信息。
对于内部签约配置序列号， 接入网设备 10在收到后不会去识别， 而是发送给 MTC设 备 30。
对于核心网设备 20, 不需要存储接入网签约配置信息，但是会存储 MTC设备 30的标 识、 内部签约配置序列号和接入网签约配置编号三者之间的对应关系， 从而可以使接入网 设备 10和 MTC设备 30识别的接入网签约配置信息保持一致。
当然， 根据需要也可以内部签约配置序列号和接入网签约配置编号相同， 这样只需要 建立 MTC设备 30的标识和内部签约配置序列号（或接入网签约配置编号）二者之间的对 应关系。
基于同一发明构思， 本申请实施例中还提供了接入网设备、核心网设备、 MTC设备及 进行建立连接的方法， 由于这些设备和方法解决问题的原理与本申请实施例进行建立连接 的系统相似， 因此这些设备和方法的实施可以参见系统的实施， 重复之处不再赘述。
如图 2所示， 本申请实施例的接入网设备包括： 确定模块 200和第一建立模块 210。 确定模块 200,用于通过核心网设备确定发起连接请求的 MTC设备的接入网签约配置 编号，根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系，确定 MTC 设备的接入网签约配置编号对应的接入网签约配置信息；
第一建立模块 210, 用于根据确定的接入网签约配置信息与 MTC设备建立连接。 较佳地， 若 MTC设备对应一个接入网签约配置信息， 在确定接入网签约配置信息之 后， 与 MTC设备建立连接之前， 确定模块 200通知 MTC设备启动接入网签约配置信息； 若 MTC设备对应多个接入网签约配置信息，在确定接入网签约配置信息之后，与 MTC 设备建立连接之前， 确定模块 200将从核心网设备获取的 MTC设备对应的内部签约配置 序列号发送给 MTC设备，用于通知 MTC设备启动内部签约配置序列号对应的接入网签约 配置信息。
较佳地， 确定模块 200确定接入网签约配置信息之前， 在确定发起连接请求的 MTC 设备未存储接入网签约配置信息后， 通过广播发送所有的接入网签约配置信息， 并通过 RRC信令通知 MTC设备所有的接入网签约配置信息中属于该 MTC设备的接入网签约配 置信息； 或
确定接入网签约配置信息之前， 在确定发起连接请求的 MTC设备未存储接入网签约 配置编号和接入网签约配置信息后，通过 RRC信令通知 MTC设备对应的接入网签约配置 信息。
较佳地， 确定模块 200向需要进行接入网签约配置信息更新的 MTC设备发起寻呼通 知 MTC设备读取系统消息， 并发送包含更新的接入网签约配置信息的系统消息； 或
在 MTC设备发起业务请求时， 通过发送包含更新的接入网签约配置信息的专用信令 通知 MTC设备更新对应的接入网签约配置信息。
较佳地， 确定模块 200根据下列方式确定需要进行更新的接入网签约配置信息： 在根据收到的来自核心网设备的需要进行更新的接入网签约配置信息对应的接入网 签约配置编号后， 确定对应的需要进行更新的接入网签约配置信息。
较佳地， 确定模块 200通过专用信令通知 MTC设备更新对应的接入网签约配置信息 之前， 在收到来自核心网设备的需要进行更新的接入网签约配置信息对应的接入网签约配 置编号后， 确定 MTC设备有更新标记。 较佳地， 确定模块 200在更新完成后， 通知核心网设备去除 MTC设备的更新标记。 较佳地， 确定模块 200将来自核心网设备的针对 MTC设备的接入网签约配置信息对 应的内部签约配置序列号转发给 MTC设备。
如图 3所示， 本申请实施例的核心网设备包括： 处理模块 300和发送模块 310。
处理模块 300,用于确定向接入网设备发起连接请求的 MTC设备的接入网签约配置编 号；
发送模块 310, 用于向接入网设备发送接入网签约配置编号， 用于通知接入网设备根 据接入网签约配置编号对应的接入网签约配置信息与 MTC设备建立连接。
较佳地， 若 MTC设备对应一个接入网签约配置信息， 根据预先设定的设备标识和接 入网签约配置编号的对应关系， 处理模块 300确定 MTC设备的设备标识对应的接入网签 约配置编号；
若 MTC设备对应多个接入网签约配置信息， 根据预先设定的设备标识、 内部签约配 置序列号和接入网签约配置编号的对应关系， 处理模块 300确定 MTC设备的设备标识和 内部签约配置序列号对应的接入网签约配置编号。
较佳地， 处理模块 300在确定发起连接请求的 MTC设备是签约用户设备后， 确定接 入网签约配置编号。
较佳地， 处理模块 300在确定向接入网设备发起连接请求的 MTC设备未存储接入网 签约配置信息后，根据预先设定的设备标识和接入网签约配置编号的对应关系，确定 MTC 设备的设备标识对应的接入网签约配置编号， 并向接入网设备发送确定的接入网签约配置 编号， 用于通知接入网设备为 MTC设备配置接入网签约配置编号对应的接入网签约配置 信息； 或根据预先设定的设备标识、 内部签约配置序列号和接入网签约配置编号的对应关 系， 确定 MTC设备的设备标识对应的内部签约配置序列号和接入网签约配置编号， 并向 接入网设备发送确定的内部签约配置序列号和接入网签约配置编号， 用于通知接入网设备 为 MTC设备配置接入网签约配置编号对应的接入网签约配置信息和内部签约配置序列号。
较佳地， 处理模块 300通知接入网设备需要为 MTC设备发送更新的接入网签约配置 信息对应的接入网签约配置编号。
较佳地， 若 MTC设备对应多个接入网签约配置信息， 处理模块 300将 MTC设备的接 入网签约配置信息对应的内部签约配置序列号发送给接入网设备 , 用于通知接入网设备将 内部签约配置序列号转发给 MTC设备。
较佳地， 处理模块 300在确定 MTC设备有更新标记后， 通知接入网设备需要为 MTC 设备发送更新的接入网签约配置信息对应的接入网签约配置编号。
较佳地， 处理模块 300在 MTC设备完成接入网签约配置信息的更新后， 去除 MTC设 备的更新标记。 如图 4所示， 本申请实施例的 MTC设备包括： 上报模块 400和第二建立模块 410。 上报模块 400 , 向接入网设备发起连接请求；
第二建立模块 410 , 用于根据对应的接入网签约配置信息与接入网设备建立连接。 较佳地， 若 MTC设备对应一个接入网签约配置信息， 上 莫块 400向接入网设备发 起包含 MTC设备对应设备标识的连接请求；
若 MTC设备对应多个接入网签约配置信息，上报模块 400向接入网设备发起包含 MTC 设备对应设备标识和建立连接需要使用的接入网签约配置信息对应的内部签约配置序列 号的连接请求。
较佳地， 上报模块 400预先存储接入网签约配置信息。
较佳地， 上 莫块 400未存储接入网签约配置信息， 若 MTC设备对应一个接入网签 约配置信息，上报模块 400存储接入网设备通知的 MTC设备对应的接入网签约配置信息； 上 ^艮模块 400未存储接入网签约配置信息， 若 MTC设备对应多个接入网签约配置信 息， 上报模块 400根据接入网设备通知的 MTC设备对应的接入网签约配置信息， 以及每 个接入网签约配置信息的顺序， 建立并存储接入网签约配置信息和内部签约配置序列号的 对应关系； 或根据接入网设备通知的 MTC设备对应的接入网签约配置信息和内部签约配 置序列号， 建立并存储接入网签约配置信息和内部签约配置序列号的对应关系。
较佳地， 若 MTC设备对应一个接入网签约配置信息， 上报模块 400根据收到的来自 接入网设备的需要进行更新的接入网签约配置信息， 更新存储的接入网签约配置信息； 若 MTC设备对应多个接入网签约配置信息， 上报模块 400根据收到的来自接入网设 备的需要进行更新的接入网签约配置信息和内部签约配置序列号， 更新存储的接入网签约 配置信息和对应的内部签约配置序列号。
如图 5所示， 本申请实施例接入网设备侧进行建立连接的方法包括：
步骤 501、接入网设备通过核心网设备确定发起连接请求的 MTC设备的接入网签约配 置编号；
步骤 502、 接入网设备根据预先设定的接入网签约配置编号和接入网签约配置信息的 对应关系， 确定 MTC设备的接入网签约配置编号对应的接入网签约配置信息；
步骤 503、 接入网设备根据确定的接入网签约配置信息与 MTC设备建立连接。
较佳地， 接入网设备确定接入网签约配置信息之后， 与 MTC设备建立连接之前还包 括：
若 MTC设备对应一个接入网签约配置信息，接入网设备通知 MTC设备启动接入网签 约配置信息；
若 MTC设备对应多个接入网签约配置信息， 接入网设备将从核心网设备获取的 MTC 设备对应的内部签约配置序列号发送给 MTC设备 ,用于通知 MTC设备启动所述内部签约 配置序列号对应的接入网签约配置信息。
较佳地， 步骤 501之前还包括：
接入网设备在确定发起连接请求的 MTC设备未存储接入网签约配置信息后， 通过广 播发送所有的接入网签约配置信息， 并通过 RRC信令通知 MTC设备所有的接入网签约配 置信息中属于该 MTC设备的接入网签约配置信息； 或
接入网设备在确定发起连接请求的 MTC设备未存储接入网签约配置编号和接入网签 约配置信息后， 通过 RRC信令通知 MTC设备对应的接入网签约配置信息。
较佳地， 若 MTC设备对应多个接入网签约配置信息， 则接入网设备在为 MTC设备配 置接入网签约配置信息时还可以将来自核心网设备的针对 MTC设备的接入网签约配置信 息对应的内部签约配置序列号转发给 MTC设备。
较佳地， 本申请实施例还可以进一步对接入网签约配置信息进行更新。
具体的， 接入网设备向需要进行接入网签约配置信息更新的 MTC设备发起寻呼通知 MTC设备读取系统消息， 并发送包含更新的接入网签约配置信息的系统消息； 或
接入网设备在 MTC设备发起业务请求时， 通过发送包含更新的接入网签约配置信息 的专用信令通知 MTC设备更新对应的接入网签约配置信息。
较佳地，接入网设备通过核心网设备确定 MTC设备有更新标记后， 确定为 MTC设备 进行更新。
较佳地， 接入网设备确定收到的来自核心网设备的接入网签约配置编号对应的需要为 MTC设备进行更新的接入网签约配置信息之后，将确定的需要进行更新的接入网签约配置 信息发送给 MTC设备。
较佳地， 接入网设备在更新完成后， 通知核心网设备去除 MTC设备的更新标记。 较佳地， 若 MTC设备对应多个接入网签约配置信息， 则接入网设备在为 MTC设备进 行更新时， 还可以将来自核心网设备的针对 MTC设备的接入网签约配置信息对应的内部 签约配置序列号转发给 MTC设备。
若本申请实施例应用于 LTE系统中， 接入网设备有如下行为：
1、 接入网存储所有类型的接入网签约配置；
2、 对于非直接存储在 MTC设备中的接入网签约配置信息， 初始 MTC设备发起建立 原因为 Mo- Signalling 的 RRCConnectionRequest ( RRC 连接请求 ） 消息， 并在 RRCConnectionSetupComplete ( RRC连接建立成功）消息中携带 Attach Request (接入请求） 消息， 当核心网设备接收到使用接入网签约配置的 MTC设备的 Attach Request后， 将该 MTC设备使用的接入网签约配置编号发给 eNB , eNB得到接入网签约配置编号后， 如果 在系统消息中广播了接入网签约配置信息（其中还包括每个接入网签约配置信息对应的接 入网签约配置编号）， 则通过 RRC Connection Setup ( RRC连接建立） 消息通知该 MTC设 备使用的接入网签约配置编号， 否则通过 RRC Connection Reconfiguration将接入网签约配 置信息和针对该 MTC设备的其他配置信息一起发送给该 MTC设备；
3、 对于使用接入网签约配置信息的 MTC设备， 可以在 RRC Connection Request消息 中增加一种建立原因， e B收到这种建立原因的 RRC Connection Request消息后， 则向核 心网设备发送接入网签约配置查询信息， 其中携带 MTC设备的标识（若 MTC设备对应多 个接入网签约配置查询信息， 还可以携带对应的内部签约配置序列号）；
4、 eNB从核心网设备获得反馈的 MTC设备的接入网签约配置编号， 通过编号查找到 对应的接入网签约配置信息， 使用该接入网签约配置信息为 MTC设备建立上下文， 使用 RRC Connection Setup消息通知 MTC设备；
5、 接入网签约配置信息包含完整的控制面和业务面配置信息， eNB 不需要再次通过 重配置过程为 MTC设备建立业务 RB;
6、 网络侧可以控制更新接入网签约配置， eNB 可以通过寻呼 +系统消息的方式通知 MTC设备更新接入网签约配置， 也可以在 MTC设备发起业务请求时， 通过专用信令下发 更新后的接入网签约配置。 若通过专用信令更新接入网签约配置， 核心网需要对 MTC设 备的接入网签约配置信息是否进行更新进行记录，当 eNB向核心网查询时，通知 eNB, eNB 向没有更新的 MTC设备发送更新后的接入网签约配置信息。
若本申请实施例应用于 UMTS中， 接入网设备有如下行为：
1、 接入网存储所有类型的接入网签约配置， 并建立接入网签约配置信息和接入网签 约配置编号的对应关系；
2、 RNC收到建立原因为 M2M签约业务的 RRC Connection Request消息后， 向核心网 设备发送接入网签约配置查询信息， 其中携带 MTC设备标识（若 MTC设备对应多个接 入网签约配置查询信息， 还可以携带对应的内部签约配置序列号）；
3、 RNC收到核心网下发的 RAB Assignment Request消息， 如果该消息携带有配置下 发指示， 则 RNC根据签约配置编号查询对应的接入网签约配置， 通过 RB Setup将接入网 签约配置信息 （还可能包括内部签约配置序列号）发送给该 MTC设备。 也可以是在系统 消息中广播接入网签约配置信息；
4、 RNC收到核心网下发的 RAB Assignment Request消息， 如果该消息有编号更新指 示， RNC得知 MTC设备的接入网签约配置信息已变更， 根据接入网签约配置编号查询对 应的接入网签约配置信息，可以通过寻呼 +系统消息的方式通知 MTC Device更新为新编号 的接入网签约配置，也可以通过 RRC Connection Setup信令下发新编号的接入网签约配置；
5、 RNC收到核心网下发的 RAB Assignment Request消息， 如果该消息既没有配置下 发指示又没有编号更新指示， 则 RNC根据接入网签约配置编号查询对应的接入网签约配 置信息， 使用 RRC Connection Setup消息通知 MTC设备， 该消息只携带除接入网签约配 置以外的 per UE内容， 再使用该接入网签约配置信息为 MTC Device建立上下文；
6、 接入网签约配置信息包含完整的控制面和业务面配置信息， MTC设备存储了接入 网签约配置信息后， RNC不需要再次通过 RB 建立过程为 MTC设备建立业务 RB。
如图 6所示， 本申请实施例核心网设备侧通知进行建立连接的方法包括下列步骤： 步骤 601、核心网设备确定向接入网设备发起连接请求的 MTC设备的接入网签约配置 编号；
步骤 602、 核心网设备向接入网设备发送接入网签约配置编号， 用于通知接入网设备 根据接入网签约配置编号对应的接入网签约配置信息与 MTC设备建立连接。
较佳地， 步骤 601 中若 MTC设备对应一个接入网签约配置信息， 核心网设备根据预 先设定的设备标识和接入网签约配置编号的对应关系， 确定 MTC设备的设备标识对应的 接入网签约配置编号；
若 MTC设备对应多个接入网签约配置信息， 核心网设备根据预先设定的设备标识、 内部签约配置序列号和接入网签约配置编号的对应关系， 确定 MTC设备的设备标识和内 部签约配置序列号对应的接入网签约配置编号。
较佳地， 核心网设备判断发起连接请求的 MTC设备是否是签约用户设备， 如果是， 则执行步骤 601。
若发起连接请求的 MTC设备未存储接入网签约配置信息， 则核心网设备根据预先设 定的设备标识和接入网签约配置编号的对应关系， 确定 MTC设备的设备标识对应的接入 网签约配置编号， 并向接入网设备发送确定的接入网签约配置编号， 用于通知接入网设备 为 MTC设备配置接入网签约配置编号对应的接入网签约配置信息； 或根据预先设定的设 备标识、 内部签约配置序列号和接入网签约配置编号的对应关系， 确定 MTC设备的设备 标识对应的内部签约配置序列号和接入网签约配置编号， 并向接入网设备发送确定的内部 签约配置序列号和接入网签约配置编号， 用于通知接入网设备为 MTC设备配置接入网签 约配置编号对应的接入网签约配置信息和内部签约配置序列号。
较佳的， 若需要连接的 MTC设备有更新标记， 则核心网设备通知接入网设备需要为
MTC设备进行更新的接入网签约配置信息对应的接入网签约配置编号。
如果 MTC设备对应多个接入网签约配置信息，核心网设备还可以将 MTC设备的接入 网签约配置信息对应的内部签约配置序列号发送给接入网设备 , 用于通知接入网设备将内 部签约配置序列号转发给 MTC设备。
较佳的，核心网设备在 MTC设备完成接入网签约配置信息的更新后， 去除 MTC设备 的更新标记。
若本申请实施例应用于 LTE系统中， 核心网有如下行为：
1、核心网设备存储所有使用接入网签约配置的 MTC设备的接入网签约配置编号和内 部签约配置序列号， 并建立 IMSI与接入网签约配置编号的对应关系， 以及 IMSI、 内部签 约配置序列号和接入网签约配置编号之间的对应关系；
2、 当核心网设备接收到 Attach Request消息后， 首先才 居 S-TMSI对应的 IMSI查询 是否为 M2M签约用户， 如果是 M2M签约用户， 则查询对应的接入网签约配置编号 （若 有内部签约配置序列号，还需要根据内部签约配置序列号进行查找）,在 Initial Context Setup Request (初始上下文建立请求） 消息中携带签约查找到的接入网接入网签约配置编号 (若 根据内部签约配置序列号进行查找，较佳地还可以携带内部签约配置序列号）， 以及配置指 示信息； 如果不是 M2M签约用户， 则不携带上述信息；
3、 当核心网设备接收到 e B发送的接入网签约配置查询消息后， 首先根据 S-TMSI 对应的 IMSI (若有内部签约配置序列号， 还需要才艮据内部签约配置序列号进行查找）， 查 询对应的接入网签约配置编号， 向 eNodeB发送 Initial Context Setup Request消息， 携带接 入网签约配置编号；
4、 网络侧可以对接入网签约配置信息进行更新， 即对 Μ2Μ签约用户变更成另一种接 入网签约配置。 核心网设备需要对 MTC设备的接入网签约配置编号是否进行了变更进行 记录， 变更一次就做上标记。 当 eNB向核心网设备查询时， 核心网设备发现有变更标记存 在，就通过 Initial Context Setup Request消息将变更后的接入网签约配置编号和编号更新指 示通知 eNB;
5、 当核心网设备接收到 Initial Context Setup Response消息，如果该消息携带配置下发 确认， 则核心网确认 MTC设备已存储接入网签约配置；
6、 当核心网设备接收到 Initial Context Setup Response消息，如果该消息携带编号更新 确认， 核心网设备确认 MTC设备已变更接入网签约配置， 则清除接入网签约配置信息的 变更标记。
若本申请实施例应用于 UMTS中， 核心网有如下行为：
1、核心网设备存储所有使用接入网签约配置的 MTC设备的接入网签约配置编号和内 部签约配置序列号， 并建立 IMSI与接入网签约配置编号的对应关系， 以及 IMSI、 内部签 约配置序列号和接入网签约配置编号之间的对应关系；
2、 当核心网设备接收到 Attach Request消息后， 首先才 居 P-TMSI对应的 IMSI查询 是否为 M2M签约用户。 如果是 M2M签约用户， 则查询对应的接入网签约配置编号 （若 有内部签约配置序列号， 还需要根据内部签约配置序列号进行查找）， 在 RAB Assignment Request (无线接入承载分配请求） 消息中携带接入网签约配置编号 (若根据内部签约配置 序列号进行查找， 较佳地还可以携带内部签约配置序列号）， 及配置下发指示； 如果不是 M2M签约用户， 则不携带上述信息；
3、 当核心网设备接收到 RNC发送的接入网签约配置查询消息后， 首先根据 P-TMSI 对应的 IMSI (若有内部签约配置序列号， 还需要才艮据内部签约配置序列号进行查找）， 查 询对应的接入网签约配置编号， 向 RNC发送 RAB Assignment Request消息， 携带接入网 签约配置编号；
4、 网络侧可以对接入网签约配置进行控制， 对 M2M签约用户变更成另一种接入网签 约配置。 即核心网设备需要对 MTC设备的接入网签约配置编号是否进行了变更进行记录， 变更一次就做上标记。 当 RNC 向核心网设备查询时， 核心网设备发现有变更标记存在， 就通过 RAB Assignment Request消息将变更后的接入网签约配置编号和编号更新指示通知 RNC;
5、 当核心网设备接收到 RAB Assignment Response消息， 如果该消息携带配置下发确 认， 则核心网确认 UE已存储接入网签约配置。
6、 当核心网设备接收到 RAB Assignment Response消息， 如果该消息携带编号更新确 认， 核心网确认 MTC设备已变更接入网签约配置， 则清除接入网签约配置的变更标记。
如图 7所示， 本申请实施例 MTC设备侧进行建立连接的方法包括下列步骤： 步骤 701、 MTC设备向接入网设备发起连接请求；
步骤 702、 MTC设备根据对应的接入网签约配置信息与接入网设备建立连接。
较佳地， 步骤 701中：
若 MTC设备对应一个接入网签约配置信息， MTC设备向接入网设备发起包含 MTC 设备对应设备标识的连接请求；
若 MTC设备对应多个接入网签约配置信息， MTC设备向接入网设备发起包含 MTC 设备对应设备标识和建立连接需要使用的接入网签约配置信息对应的内部签约配置序列 号的连接请求。
在实施中， MTC设备可以预先存储接入网签约配置信息。
若 MTC设备未存储接入网签约配置信息； 步骤 701之前还可以进一步包括： 若 MTC设备对应一个接入网签约配置信息， MTC设备存储接入网设备通知的 MTC 设备对应的接入网签约配置信息；
若 MTC设备对应多个接入网签约配置信息， MTC设备根据接入网设备通知的 MTC 设备对应的接入网签约配置信息， 以及每个接入网签约配置信息的顺序， 建立并存储接入 网签约配置信息和内部签约配置序列号的对应关系； 或根据接入网设备通知的 MTC设备 对应的接入网签约配置信息和内部签约配置序列号， 建立并存储接入网签约配置信息和内 部签约配置序列号的对应关系。
较佳地， 若 MTC设备对应一个接入网签约配置信息， MTC设备根据收到的来自接入 网设备的需要进行更新的接入网签约配置信息， 更新存储的接入网签约配置信息。
较佳地， 若 MTC设备对应多个接入网签约配置信息， MTC设备根据收到的来自接入 网设备的需要进行更新的接入网签约配置信息和对应的内部签约配置序列号， 更新存储的 接入网签约配置信息和对应的内部签约配置序列号。
较佳地， 若 MTC设备对应多个接入网签约配置信息， MTC设备根据接入网签约配置 信息的顺序或收到的内部签约配置序列号， 确定需要进行更新的接入网签约配置信息。
若本申请实施例应用于 LTE系统中， MTC设备有如下行为：
1、 MTC设备内如果没有存储接入网签约配置信息， 则发起建立原因为 mo-Signalling 的 RRC Connection Request消息。
2、 MTC设备接收到含有接入网签约配置信息的 RRC Connection Setup 消息 / RRC Connection Reconfiguration消息后， 将接入网签约配置保存下来；
3、 存储了接入网签约配置的 MTC 设备需要进行业务传输， 则发起
RRCConnectionRequest。 支持多种接入网签约配置信息的 MTC设备， 在发起接入时， 可 以携带内部接入网签约配置序列号；
4、 MTC设备接收到 RRC Connection Setup消息后就可以直接使用接入网签约配置进 行信令和数据的传输过程， 如果收到的 RRC Connection Setup消息中带有完整接入网签约 配置信息， 则更新存储的接入网签约配置。
5、 MTC设备接收到用于通知接入网签约配置信息改变的 paging (寻呼）， 则读取系统 信息， 更新存储的接入网签约配置信息。
若本申请实施例应用于 UMTS中， MTC设备有如下行为：
1、 MTC设备内如果没有存储接入网签约配置信息， 则发起建立原因为 Registration的 RRC Connection Request;
2、 MTC 设备内如果已经存储接入网签约配置信息， 要进行数据发送， 则在 RRC Connection Request中使用新的建立原因—— M2M签约业务；
3、 MTC设备接收到含有接入网签约配置信息和针对自身的其他配置信息的 RB Setup 后， MTC设备将接入网签约配置保存下来。 如果有多套接入网签约配置， 则 MTC设备将 接收到的多套接入网签约配置和对应的内部签约配置序列号进行保存， 并建立接入网签约 配置和内部签约配置序列号的对应关系；
4、 MTC设备接收到 RRC Connection Setup后， 如果 RRC Connection Setup消息里只 有除接入网签约配置信息以外的 per UE内容， 就可以直接使用已存储的接入网签约配置； 如果 RRC Connection Setup消息里有完整接入网签约配置信息， 则更新存储的接入网签约 配置， 并使用；
5、 支持多种接入网签约配置信息的 MTC设备， 在发起接入时， 可以携带内部签约配 置序列号。 如果接收到的 RRC Connection Setup消息里只有除接入网签约配置以外的 per UE内容，则 MTC设备根据发起接入时的内部签约配置序列号直接使用其关联的已存储的 接入网签约配置； 如果 RRC Connection Setup消息里有完整接入网签约配置信息， 则 MTC 设备根据发起接入时的内部签约配置序列号更新其关联的已存储的接入网签约配置， 并使 用；
6、 MTC设备接收到用于通知接入网签约配置信息改变的 paging (寻呼）， 则读取系统 信息， 更新存储的接入网签约配置信息。
下面以具体实例对本申请的方案进行说明。
如图 8所示， 本申请实施例 LTE系统 MTC设备通过信令获取接入网签约配置信息的 方法包括下列步骤：
步骤 801、UE向 e B发送建立原因为 mo-Signalling,且包含 S-TMSI的 RRC Connection Request ( RRC连接请求） 消息；
步骤 802、 eNB向 UE返回 RRC Connection Setup ( RRC连接建立） 消息；
步骤 803、 UE向 eNB发送 RRC Connection Setup Complete ( RRC连接建立成功） 消 息和 NAS Attach Request (非接入层接入请求） 消息；
步骤 804、 eNB向 MME发送包含 S-TMSI的 NAS Attach Request消息；
步骤 805、 MME对 S-TMSI对应的 UE进行 Authentication/NAS Security Mode Control
(鉴权 /非接入层安全模式控制）；
步骤 806、 MME在确定 UE是 M2M的签约用户后， 确定 UE对应的接入网签约配置 编号， 并向 eNB返回包含接入网签约配置编号的 Initial Context Setup Request (初始上下文 建立请求） 消息和 NAS Attach Accept消息；
步骤 807、 eNB根据接入网签约配置编号查找对应的接入网签约配置信息；
步骤 808、 eNB向 UE发送 AS Security Mode Command (接入层安全模式命令）消息； 步骤 809、 UE向 eNB返回 AS Security Mode Complete (接入层安全模式成功 ) 消息； 步骤 810、 eNB向 UE发送包含接入网签约配置信息的 RRC Connection Reconfiguration ( RRC连接确认） 消息和 NAS Attach Accept消息；
步骤 811、 UE存储收到的接入网签约配置信息；
步骤 812、 UE向 eNB发送 RRC Connection Reconfiguration Complete消息； 步骤 813、 eNB向 MME发送 Initial Context Setup Response消息；
步骤 814、 UE向 eNB发送 NAS Attach Complete消息；
步骤 815、 eNB向 MME发送 NAS Attach Complete消息。
其中， 如果 UE支持多个接入网签约配置信息， 较佳地， 步骤 806和步骤 810中还可 以携带对应的内部签约配置序列号。
如图 9所示， 本申请实施例 LTE系统只有一套接入网签约配置信息的 MTC设备使用 接入网签约配置信息建立连接的方法包括下列步骤： 步骤 901、 UE向 eNB发送包含 S-TMSI的 RRC Connection Request消息； 步骤 902、 eNB向 MME发送包含 S-TMSI的接入网签约配置查询消息；
步骤 903、 MME根据 S-TMSI确定 UE对应的接入网签约配置编号， 并向 eNB返回包 含接入网签约配置编号的 Initial Context Setup Request消息；
步骤 904、 eNB根据接入网签约配置编号查找对应的接入网签约配置信息， 并根据接 入网签约配置信息为 UE建立上下文；
步骤 905、 eNB向 UE发送 RRC Connection Setup消息；
可选的， 步骤 906、 eNB向 UE发送 AS Security Mode Command消息；
可选的， 步骤 907、 UE向 eNB返回 AS Security Mode Complete消息；
步骤 908、 UE和 eNB启用接入网签约配置信息；
步骤 909、 UE向 eNB发送 RRC Connection Setup Complete消息；
步骤 910、 eNB向 MME发送 Initial Context Setup Complete消息。
其中，若不执行步骤 906 ~步骤 907,则步骤 905中 eNB还可以在 RRC Connection Setup 消息中携带 AS Security Mode Command消息的内容； 相应的 , 在步骤 909中, UE还可以 在 RRC Connection Setup Complete消息中携带 AS Security Mode Complete消息的内容。
如图 10所示，本申请实施例 LTE系统有多套接入网签约配置信息的 MTC设备使用接 入网签约配置信息建立连接的方法包括下列步骤：
步骤 1001、 UE向 eNB发送包含 S-TMSI和需要启用的接入网配置信息对应的内部签 约配置序列号的 RRC Connection Request消息；
步骤 1002、 eNB向 MME发送包含 S-TMSI和内部签约配置序列号的接入网签约配置 查询消息；
步骤 1003、 MME根据 S-TMSI和内部签约配置序列号确定 UE对应的接入网签约配 置编号， 并向 eNB返回包含接入网签约配置编号的 Initial Context Setup Request消息； 步骤 1004、 eNB根据接入网签约配置编号查找对应的接入网签约配置信息， 并根据接 入网签约配置信息为 UE建立上下文；
步骤 1005、 eNB向 UE发送 RRC Connection Setup消息；
可选的， 步骤 1006、 eNB向 UE发送 AS Security Mode Command消息；
可选的 , 步骤 1007、 UE向 eNB返回 AS Security Mode Complete消息；
步骤 1008、 eNB启用接入网签约配置信息， UE启用内部签约配置序列号对应的接入 网签约配置信息；
步骤 1009、 UE向 eNB发送 RRC Connection Setup Complete消息；
步骤 1010、 eNB向 MME发送 Initial Context Setup Complete消息。
其中，若不执行步骤 1006 ~步骤 1007， 则步骤 1005中 eNB还可以在 RRC Connection Setup消息中携带 AS Security Mode Command消息的内容； 相应的 , 在步骤 1009中 , UE 还可以在 RRC Connection Setup Complete消息中携带 AS Security Mode Complete消息的内 容。
其中， 若步骤 1003中， Initial Context Setup Request消息中包含内部签约配置序列号， 则步骤 1005中， RRC Connection Setup消息中也可以包含内部签约配置序列号。
其中， 若步骤 1005中， RRC Connection Setup消息中包含内部签约配置序列号， 步骤 1008 中， UE 启动内部签约配置序列号对应的接入网签约配置信息， 若 RRC Connection Setup消息中不包含内部签约配置序列号， 步骤 1008中， UE启动初始选择的接入网签约 配置信息。
如图 11所示， 本申请实施例 LTE系统变更 MTC设备的接入网签约配置信息的方法 流程示意图；
步骤 1101、 UE向 eNB发送包含 S-TMSI的 RRC Connection Request消息；
步骤 1102、 eNB向 MME发送包含 S-TMSI的接入网签约配置查询消息；
步骤 1103、 MME在确定 UE有更新标记后，根据 S-TMSI和内部签约配置序列号确定 UE对应的需要更新的接入网签约配置编号， 并向 eNB返回包含接入网签约配置编号和变 更指示的 Initial Context Setup Request消息；
步骤 1104、 eNB根据接入网签约配置编号查找对应的接入网签约配置信息， 并根据接 入网签约配置信息为 UE建立上下文；
步骤 1105、 eNB向 UE发送 RRC Connection Setup消息；
可选的， 步骤 1006、 eNB向 UE发送 AS Security Mode Command消息；
可选的， 步骤 1007、 UE向 eNB返回 AS Security Mode Complete消息；
步骤 1108、 eNB启用接入网签约配置信息， UE根据收到的接入网签约配置信息和对 应的内部签约配置序列号进行更新， 并启动收到的接入网签约配置信息；
步骤 1109、 UE向 eNB发送 RRC Connection Setup Complete消息；
步骤 1110、 eNB向 MME发送 Initial Context Setup Complete消息。
步骤 1111、 MME清除 UE的更新标记。
其中， 若不执行步骤 1106 -步骤 1107, 则步骤 1105中 eNB还可以在 RRC Connection Setup消息中携带 AS Security Mode Command消息的内容； 相应的， 在步骤 1109中， UE 还可以在 RRC Connection Setup Complete消息中携带 AS Security Mode Complete消息的内 容。
其中， 若 UE支持多个接入网签约配置信息， 较佳地， 步骤 1101中， RRC Connection Request消息消息中包含内部签约配置序列号； 步骤 1003中， Initial Context Setup Request 消息中包含需要更新的接入网签约配置信息对应的内部签约配置序列号， 则步骤 1005中， RRC Connection Setup消息中也可以包含内部签约配置序列号。
较佳地， 需要更新的接入网签约配置信息是 UE发送的内部签约配置序列号对应的接 入网签约配置信息。
如图 12所示，本申请实施例 UMTS系统只有一套接入网签约配置信息的 MTC设备通 过信令获取接入网签约配置信息的方法包括下列步骤：
步骤 1201、 UE向 RNC发送包含 P-TMSI的 RRC Connection Request消息； 步骤 1202、 RNC向 UE返回 RRC Connection Setup消息；
步骤 1203、 UE向 RNC发送 RRC Connection Setup Complete消息；
步骤 1204、 UE向 RNC发送 NAS Attach Request消息；
步骤 1205、 RNC向 SGSN发送包含 P-TMSI的 NAS Attach Request消息；
步骤 1206、 SGSN在确定 UE是 M2M的签约用户后， 确定 UE对应的接入网签约配 置编号；
步骤 1207、 SGSN通过 RNC对 UE进行 Authentication;
步骤 1208、 SGSN通过 RNC对 UE进行 NAS Security Mode Control;
步骤 1209、 SGSN向 RNC发送 NAS Attach Accept消息；
步骤 1210、 RNC向 UE发送 NAS Attach Accept消息；
步骤 1211、 UE向 RNC发送 NAS Attach Complete消息；
步骤 1212、 RNC向 SGSN发送 NAS Attach Complete消息；
步骤 1213、 UE向 RNC发送 NAS Active PDP Context Request (非接入层主动数据包协 议上下文请求） 消息；
步骤 1214、 RNC向 SGSN发送 NAS Active PDP Context Request消息；
步骤 1215、 SGSN向 RNC发送包含接入网签约配置编号和配置指示的 RAB Assignment
Request (无线接入承载分配请求） 消息；
步骤 1216、 RNC根据接入网签约配置编号查找对应的接入网签约配置信息； 步骤 1217、 RNC向 UE发送包含接入网签约配置信息的 Radio Bearer Setup (无线承载 建立） 消息；
步骤 1218、 UE存储收到的接入网签约配置信息；
步骤 1219、 UE向 RNC发送 Radio Bearer Setup Complete消息；
步骤 1220、 RNC向 SGSN发送包含配置确认信息的 RAB Assignment Response消息； 步骤 1221、 SGSN向 RNC发送 NAS Active PDP Context Accept消息；
步骤 1222、 RNC向 UE发送 NAS Active PDP Context Accept消息。
如图 13所示，本申请实施例 UMTS系统只有一套接入网签约配置信息的 MTC设备使 用接入网签约配置信息建立连接的方法包括下列步骤： 步骤 1301、 UE 向 RNC 发送包含建立原因为 M2M签约业务和 P-TMSI 的 RRC
Connection Request消息；
步骤 1302、 RNC向 SGSN发送包含 P-TMSI的接入网签约配置查询消息；
步骤 1303、 SGSN根据 P-TMSI确定 UE对应的接入网签约配置编号， 并向 eNB返回 包含接入网签约配置编号的 RAB Assignment Request消息；
步骤 1304、 RNC根据接入网签约配置编号查找对应的接入网签约配置信息； 步骤 1305、 RNC向 UE发送 RRC Connection Setup消息；
步骤 1306、 UE和 RNC启用接入网签约配置信息；
步骤 1307、 UE向 RNC发送 RRC Connection Setup Complete消息；
步骤 1308、 RNC向 SGSN发送包含配置确认信息的 RAB Assignment Response消息； 步骤 1309、 SGSN向 RNC发送 Ranap Security Mode Command ( RAN应用协议安全模 式命令） 消息；
步骤 1310、 RNC向 UE发送 RRC Security Mode Command消息；
步骤 1311、 UE向 RNC发送 RRC Security Mode Copmlete消息；
步骤 1312、 RNC向 SGSN发送 Ranap Security Mode Copmlete消息；
步骤 1313、 UE向 RNC发送 NAS Active PDP Context Request消息；
步骤 1314、 RNC向 SGSN发送 NAS Active PDP Context Request消息；
步骤 1315、 SGSN向 RNC发送 NAS Active PDP Context Accept消息；
步骤 1316、 RNC向 UE发送 NAS Active PDP Context Accept消息。
如图 14所示， 本申请实施例 UMTS系统只有一套接入网签约配置信息变更 MTC设 备的接入网签约配置信息的方法包括下列步骤：
步骤 1401、 UE 向 RNC 发送包含建立原因为 M2M签约业务和 P-TMSI 的 RRC
Connection Request消息；
步骤 1402、 RNC向 SGSN发送包含 P-TMSI的接入网签约配置查询消息；
步骤 1403、 SGSN确定该 UE有更新标记， 根据 P-TMSI确定 UE对应的需要更新的 接入网签约配置编号， 并向 eNB 返回包含接入网签约配置编号和更新指示的 RAB
Assignment Request消息；
步骤 1404、 RNC根据接入网签约配置编号查找对应的接入网签约配置信息； 步骤 1405、 RNC向 UE发送包含接入网签约配置信息的 RRC Connection Setup消息； 步骤 1406、 RNC启用接入网签约配置信息， UE根据收到的接入网签约配置信息进行 更新， 并启动收到的接入网签约配置信息；
步骤 1407、 UE向 RNC发送 RRC Connection Setup Complete消息；
步骤 1408、 RNC向 SGSN发送包含更新确认信息的 RAB Assignment Response消息； 步骤 1409、 SGSN清除 UE的更新标记；
步骤 1410、 SGSN向 RNC发送 Ranap Security Mode Command消息；
步骤 1411、 RNC向 UE发送 RRC Security Mode Command消息；
步骤 1412、 UE向 RNC发送 RRC Security Mode Copmlete消息；
步驟 1413、 RNC向 SGSN发送 Ranap Security Mode Copmlete消息；
步骤 1414、 UE向 RNC发送 NAS Active PDP Context Request消息；
步骤 1415、 RNC向 SGSN发送 NAS Active PDP Context Request消息；
步骤 1416、 SGSN向 RNC发送 NAS Active PDP Context Accept消息；
步骤 1417、 RNC向 UE发送 NAS Active PDP Context Accept消息。
如图 15所示，本申请实施例 UMTS系统有多套接入网签约配置信息的 MTC设备通过 信令获取接入网签约配置信息的方法包括下列步骤：
步骤 1501、 UE向 RNC发送包含 P-TMSI的 RRC Connection Request消息； 步骤 1502、 RNC向 UE返回 RRC Connection Setup消息；
步骤 1503、 UE向 RNC发送 RRC Connection Setup Complete消息；
步骤 1504、 UE向 RNC发送 NAS Attach Request消息；
步骤 1505、 RNC向 SGSN发送包含 P-TMSI的 NAS Attach Request消息；
步骤 1506、 SGSN在确定 UE是 M2M的签约用户后， 确定 UE对应的接入网签约配 置编号和内部签约配置序列号；
步骤 1507、 SGSN通过 RNC对 UE进行 Authentication;
步骤 1508、 SGSN通过 RNC对 UE进行 NAS Security Mode Control;
步骤 1509、 SGSN向 RNC发送 NAS Attach Accept消息；
步骤 1510、 RNC向 UE发送 NAS Attach Accept消息；
步骤 1511、 UE向 RNC发送 NAS Attach Complete消息；
步骤 1512、 RNC向 SGSN发送 NAS Attach Complete消息；
步骤 1513、 UE向 RNC发送 NAS Active PDP Context Request消息；
步骤 1514、 RNC向 SGSN发送 NAS Active PDP Context Request消息；
步骤 1515、 SGSN向 RNC发送包含接入网签约配置编号、 内部签约配置序列号和配 置指示的 RAB Assignment Request消息；
步骤 1516、 RNC根据接入网签约配置编号查找对应的接入网签约配置信息； 步骤 1517、 RNC向 UE发送包含接入网签约配置信息和内部签约配置序列号的 Radio
Bearer Setup消息；
步骤 1518、 UE建立并存储收到的接入网签约配置信息和内部签约配置序列号的对应 关系； 步骤 1519、 UE向 RNC发送 Radio Bearer Setup Complete消息；
步骤 1520、 RNC向 SGSN发送包含配置确认信息的 RAB Assignment Response消息； 步骤 1521、 SGSN向 RNC发送 NAS Active PDP Context Accept消息；
步骤 1522、 RNC向 UE发送 NAS Active PDP Context Accept消息。
如图 16所示，本申请实施例 UMTS系统有多套接入网签约配置信息的 MTC设备使用 接入网签约配置信息建立连接的方法包括下列步骤：
步骤 1601、 UE向 RNC发送包含建立原因为 M2M签约业务、 P-TMSI和需要启用的 接入网配置信息对应的内部签约配置序列号的 RRC Connection Request消息；
步骤 1602、 RNC向 SGSN发送包含 P-TMSI和内部签约配置序列号的接入网签约配置 查询消息；
步骤 1603、 SGSN根据 P-TMSI和内部签约配置序列号确定 UE对应的接入网签约配 置编号， 并向 eNB返回包含接入网签约配置编号的 RAB Assignment Request消息；
步骤 1604、 RNC根据接入网签约配置编号查找对应的接入网签约配置信息； 步骤 1605、 RNC向 UE发送 RRC Connection Setup消息；
步骤 1606、 RNC启用接入网签约配置信息， UE启用内部签约配置序列号对应的接入 网签约配置信息；
步骤 1607、 UE向 RNC发送 RRC Connection Setup Complete消息；
步骤 1608、 RNC向 SGSN发送包含配置确认信息的 RAB Assignment Response消息； 步骤 1609、 SGSN向 RNC发送 Ranap Security Mode Command消息；
步骤 1610、 RNC向 UE发送 RRC Security Mode Command消息；
步骤 1611、 UE向 RNC发送 RRC Security Mode Copmlete消息；
步骤 1612、 RNC向 SGSN发送 Ranap Security Mode Copmlete消息；
步骤 1613、 UE向 RNC发送 NAS Active PDP Context Request消息；
步骤 1614、 RNC向 SGSN发送 NAS Active PDP Context Request消息；
步骤 1615、 SGSN向 RNC发送 NAS Active PDP Context Accept消息；
步骤 1616、 RNC向 UE发送 NAS Active PDP Context Accept消息。
其中，步骤 1603中， RAB Assignment Request消息中还可以包括内部签约配置序列号， 则步骤 1605中， RRC Connection Setup消息中还包括内部签约配置序列号, 则步骤 1606 中， UE启用内部签约配置序列号对应的接入网配置信息，
如图 17所示， 本申请实施例 UMTS系统有多套接入网签约配置信息变更 MTC设备 的接入网签约配置信息的方法包括下列步骤：
步骤 1701、 UE向 RNC发送包含建立原因为 M2M签约业务、 P-TMSI和需要启用的 接入网配置信息对应的内部签约配置序列号的 RRC Connection Request消息； 步骤 1702、 RNC向 SGSN发送包含 P-TMSI和内部签约配置序列号的接入网签约配置 查询消息；
步骤 1703、 SGSN确定该 UE有更新标记， 根据 P-TMSI和内部签约配置序列号确定 UE对应的需要更新的接入网签约配置编号， 并向 eNB返回包含接入网签约配置编号、 需 要更新的接入网签约配置信息对应的内部签约配置序列号和更新指示的 RAB Assignment Request消息；
较佳地， 需要更新的接入网签约配置信息对应的内部签约配置序列和 SGSN收到的内 部签约配置序列相同。
步骤 1704、 RNC根据接入网签约配置编号查找对应的接入网签约配置信息； 步骤 1705、 RNC向 UE发送包含内部签约配置序列号和接入网签约配置信息的 RRC Connection Setup消息；
步骤 1706、 RNC启用接入网签约配置信息， UE根据收到的接入网签约配置信息和对 应的内部签约配置序列号进行更新， 并启动收到的接入网签约配置信息；
步骤 1707、 UE向 RNC发送 RRC Connection Setup Complete消息；
步骤 1708、 RNC向 SGSN发送包含更新确认信息的 RAB Assignment Response消息； 步骤 1709、 SGSN清除给 UE的更新标记；
步骤 1710、 SGSN向 RNC发送 Ranap Security Mode Command消息；
步骤 1711、 RNC向 UE发送 RRC Security Mode Command消息；
步骤 1712、 UE向 RNC发送 RRC Security Mode Copmlete消息；
步骤 1713、 RNC向 SGSN发送 Ranap Security Mode Copmlete消息；
步骤 1714、 UE向 RNC发送 NAS Active PDP Context Request消息；
步骤 1715、 RNC向 SGSN发送 NAS Active PDP Context Request消息；
步骤 1716、 SGSN向 RNC发送 NAS Active PDP Context Accept消息；
步骤 1717、 RNC向 UE发送 NAS Active PDP Context Accept消息。
图 13和图 16中的步骤 13〜步骤 16 PDP上下文激活过程，以及图 14和图 17中的步骤 14〜步骤 17 PDP上下文激活过程都是可选的， 是否出现该过程如下所示：
在图 12和图 15 , MTC设备通过信令获取接入网签约配置过程完成后， 此时 PDP激 活且 RAB建立， 之后分两种场景：
场景一、 即网络侧执行 Iu Release Request过程（原因为 User Inactivity ), PDP上下文 保留且 RAB释放 ,则 MTC设备使用接入网签约配置建立连接过程对应的图 13和图 16中 的步骤 13〜步骤 16 PDP上下文激活过程不出现， 变更 MTC设备接入网签约配置编号过程 对应的图 14和图 17中的步骤 14〜步骤 17 PDP上下文激活过程不出现；
场景二、 网络侧执行 PDP去激活过程， PDP上下文去激活且 RAB释放， 则 MTC设 备使用接入网签约配置建立连接过程对应的图 13和图 16中的步骤 13〜步骤 16 PDP上下文 激活过程必须出现， 变更 MTC Device接入网签约配置编号过程对应的图 14和图 17中的 步骤 14〜步骤 17 PDP上下文激活过程必须出现。
本领域内的技术人员应明白， 本申请的实施例可提供为方法、 系统、 或计算机程序产 品。 因此， 本申请可釆用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实 施例的形式。 而且， 本申请可釆用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介盾 （包括但不限于磁盘存储器、 CD-ROM、 光学存储器等）上实施的计算机程 序产品的形式。
本申请是参照根据本申请实施例的方法、 设备（系统）、 和计算机程序产品的流程图 和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图和 /或方框图中的每一流 程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机 程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器 以产生一个机器， 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用 于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中， 使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品， 该指令装置实现在流程图一个流程或多个流程和 /或方框图一个方框或多个 方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上， 使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理， 从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和 /或方框图一个 方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例， 但本领域内的技术人员一旦得知了基本创造性概 念， 则可对这些实施例作出另外的变更和修改。 所以， 所附权利要求意欲解释为包括优选 实施例以及落入本申请范围的所有变更和修改。
显然， 本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和 范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内， 则本申请也意图包含这些改动和变型在内。

Claims

1、 一种建立连接的方法， 其特征在于， 该方法包括：
接入网设备通过核心网设备确定发起连接请求的机器类型 MTC设备的接入网签约配 置编号；
接入网设备根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系， 确定所述 MTC设备的接入网签约配置编号对应的接入网签约配置信息；
所述接入网设备根据确定的接入网签约配置信息与所述 MTC设备建立连接。
2、 如权利要求 1 所述的方法， 其特征在于， 所述接入网设备确定接入网签约配置信 息之后， 与所述 MTC设备建立连接之前还包括；
若所述 MTC设备对应一个接入网签约配置信息，所述接入网设备通知所述 MTC设备 启动所述接入网签约配置信息；
若所述 MTC设备对应多个接入网签约配置信息， 所述接入网设备将从所述核心网设 备获取的所述 MTC设备对应的内部签约配置序列号发送给所述 MTC设备，用于通知所述
MTC设备启动所述内部签约配置序列号对应的所述接入网签约配置信息。
3、 如权利要求 1 所述的方法， 其特征在于， 所述接入网设备确定接入网签约配置信 息之前还包括：
所述接入网设备在确定发起连接请求的 MTC设备未存储接入网签约配置信息后， 通 过广播发送所有的接入网签约配置信息， 并通过 RRC信令通知所述 MTC设备所有的接入 网签约配置信息中属于所述 MTC设备的接入网签约配置信息； 或
所述接入网设备在确定发起连接请求的 MTC设备未存储接入网签约配置编号和接入 网签约配置信息后， 通过 RRC信令通知所述 MTC设备对应的接入网签约配置信息。
4、 如权利要求 1所述的方法， 其特征在于， 该方法还包括：
所述接入网设备向需要进行接入网签约配置信息更新的 MTC设备发起寻呼通知 MTC 设备读取系统消息， 并发送包含更新的接入网签约配置信息的系统消息； 或
所述接入网设备在所述 MTC设备发起业务请求时， 通过发送包含更新的接入网签约 配置信息的专用信令通知 MTC设备更新对应的接入网签约配置信息。
5、 如权利要求 4 所述的方法， 其特征在于， 所述接入网设备根据下列方式确定需要 进行更新的接入网签约配置信息：
所述接入网设备根据收到的来自所述核心网设备的需要进行更新的接入网签约配置 信息对应的接入网签约配置编号， 确定对应的需要进行更新的接入网签约配置信息。
6、 如权利要求 4所述的方法， 其特征在于， 所述接入网设备通过专用信令通知 MTC 设备更新对应的接入网签约配置信息之前还包括：
所述接入网设备在收到来自所述核心网设备的需要进行更新的接入网签约配置信息 对应的接入网签约配置编号后， 确定所述 MTC设备有更新标记。
7、 如权利要求 6所述的方法， 其特征在于， 该方法还包括：
所述接入网设备在更新完成后，通知所述核心网设备去除所述 MTC设备的更新标记。
8、 如权利要求 3或 4所述的方法， 其特征在于， 该方法还包括：
所述接入网设备将来自所述核心网设备的针对所述 MTC设备的接入网签约配置信息 对应的内部签约配置序列号转发给所述 MTC设备。
9、 如权利要求 1 ~ 7任一所述的方法， 其特征在于， 所述接入网签约配置信息包括下 列信息中的至少一种：
信令无线承载 SRB信息、 数据无线承载 DRB信息、 无线承载 RB信息、 分组数据聚 合协议 PDCP信息， 无线链路控制 RLC信息， 媒体接入控制 MAC信息和物理层的配置参 数。
10、 一种建立连接的方法， 其特征在于， 该方法包括：
核心网设备确定向接入网设备发起连接请求的 MTC设备的接入网签约配置编号； 所述核心网设备向所述接入网设备发送所述接入网签约配置编号， 用于通知所述接入 网设备根据所述接入网签约配置编号对应的接入网签约配置信息与所述 MTC设备建立连 接。
11、如权利要求 10所述的方法， 其特征在于， 所述核心网设备确定接入网签约配置编 号包括：
若所述 MTC设备对应一个接入网签约配置信息， 所述核心网设备根据预先设定的设 备标识和接入网签约配置编号的对应关系， 确定所述 MTC设备的设备标识对应的接入网 签约配置编号；
若所述 MTC设备对应多个接入网签约配置信息， 所述核心网设备根据预先设定的设 备标识、 内部签约配置序列号和接入网签约配置编号的对应关系， 确定所述 MTC设备的 设备标识和内部签约配置序列号对应的接入网签约配置编号。
12、 如权利要求 10或 11所述的方法， 其特征在于， 所述核心网设备确定接入网签约 配置编号之前还包括：
所述核心网设备确定发起连接请求的 MTC设备是签约用户设备。
13、 如权利要求 10 所述的方法， 其特征在于， 所述核心网设备确定接入网签约配置 编号之前还包括：
所述核心网设备在确定向所述接入网设备发起连接请求的 MTC设备未存储接入网签 约配置信息后， 根据预先设定的设备标识和接入网签约配置编号的对应关系， 确定所述 MTC设备的设备标识对应的接入网签约配置编号，并向所述接入网设备发送确定的接入网 签约配置编号， 用于通知所述接入网设备为所述 MTC设备配置所述接入网签约配置编号 对应的接入网签约配置信息； 或根据预先设定的设备标识、 内部签约配置序列号和接入网 签约配置编号的对应关系， 确定所述 MTC设备的设备标识对应的内部签约配置序列号和 接入网签约配置编号， 并向所述接入网设备发送确定的内部签约配置序列号和接入网签约 配置编号， 用于通知所述接入网设备为所述 MTC设备配置所述接入网签约配置编号对应 的接入网签约配置信息和内部签约配置序列号。
14、 如权利要求 10所述的方法， 其特征在于， 该方法还包括：
所述核心网设备通知所述接入网设备需要为所述 MTC设备进行更新的接入网签约配 置信息对应的接入网签约配置编号。
15、 如权利要求 14所述的方法， 其特征在于， 该方法还包括：
若所述 MTC设备对应多个接入网签约配置信息，所述核心网设备将所述 MTC设备的 接入网签约配置信息对应的内部签约配置序列号发送给所述接入网设备 , 用于通知所述接 入网设备将所述内部签约配置序列号转发给所述 MTC设备。
16、 如权利要求 14 所述的方法， 其特征在于， 所述核心网设备通知接入网签约配置 编号之前还包括：
所述核心网设备确定所述 MTC设备有更新标记。
17、 如权利要求 16所述的方法， 其特征在于， 该方法还包括：
所述核心网设备在所述 MTC设备完成接入网签约配置信息的更新后，去除所述 MTC 设备的更新标记。
18、 一种建立连接的方法， 其特征在于， 该方法包括：
MTC设备向接入网设备发起连接请求；
所述 MTC设备根据对应的接入网签约配置信息与所述接入网设备建立连接。
19、 如权利要求 18所述的方法， 其特征在于， 所述 MTC设备向接入网设备发起连接 请求包括：
若所述 MTC设备对应一个接入网签约配置信息，所述 MTC设备向接入网设备发起包 含所述 MTC设备的设备标识的连接请求；
若所述 MTC设备对应多个接入网签约配置信息，所述 MTC设备向接入网设备发起包 含所述 MTC设备的设备标识和建立连接需要使用的接入网签约配置信息对应的内部签约 配置序列号的连接请求。
20、 如权利要求 18所述的方法， 其特征在于， 所述 MTC设备预先存储接入网签约配 置信息。
21、 如权利要求 20所述的方法， 其特征在于， 所述 MTC设备未存储接入网签约配置 信息；
所述 MTC设备向接入网设备发起连接请求之前还包括：
若所述 MTC设备对应一个接入网签约配置信息，所述 MTC设备存储所述接入网设备 通知的所述 MTC设备对应的接入网签约配置信息；
若所述 MTC设备对应多个接入网签约配置信息，所述 MTC设备根据所述接入网设备 通知的所述 MTC设备对应的接入网签约配置信息，以及每个接入网签约配置信息的顺序， 建立并存储接入网签约配置信息和内部签约配置序列号的对应关系； 或根据所述接入网设 备通知的所述 MTC设备对应的接入网签约配置信息和内部签约配置序列号， 建立并存储 接入网签约配置信息和内部签约配置序列号的对应关系。
22、 如权利要求 18所述的方法， 其特征在于， 该方法还包括：
若所述 MTC设备对应一个接入网签约配置信息，所述 MTC设备根据收到的来自所述 接入网设备的需要进行更新的接入网签约配置信息， 更新存储的接入网签约配置信息； 若所述 MTC设备对应多个接入网签约配置信息，所述 MTC设备根据收到的来自所述 接入网设备的需要进行更新的接入网签约配置信息和内部签约配置序列号， 更新存储的接 入网签约配置信息和对应的内部签约配置序列号。
23、 如权利要求 18 - 22任一所述的方法， 其特征在于， 所述接入网签约配置信息包 括下列信息中的至少一种：
SRB信息、 DRB信息、 RB信息、 PDCP信息， RLC信息， MAC信息和物理层的配 置参数。
24、 一种建立连接的接入网设备， 其特征在于， 该接入网设备包括：
处理模块， 用于通过核心网设备确定发起连接请求的 MTC设备的接入网签约配置编 号， 根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系， 确定所述 MTC设备的接入网签约配置编号对应的接入网签约配置信息；
第一建立模块， 用于根据确定的接入网签约配置信息与所述 MTC设备建立连接。
25、 如权利要求 24所述的设备， 其特征在于， 所述处理模块还用于：
若所述 MTC设备对应一个接入网签约配置信息， 在确定接入网签约配置信息之后， 与所述 MTC设备建立连接之前， 通知所述 MTC设备启动所述接入网签约配置信息； 若所述 MTC设备对应多个接入网签约配置信息， 在确定接入网签约配置信息之后， 与所述 MTC设备建立连接之前，将从所述核心网设备获取的所述 MTC设备对应的内部签 约配置序列号发送给所述 MTC设备 ,用于通知所述 MTC设备启动所述内部签约配置序列 号对应的所述接入网签约配置信息。
26、 如权利要求 24所述的设备， 其特征在于， 所述处理模块还用于：
在确定发起连接请求的 MTC设备未存储接入网签约配置信息后， 通过广播发送所有 的接入网签约配置信息，并通过 RRC信令通知所述 MTC设备从广播中读取属于所述 MTC 设备的接入网签约配置信息； 或
确定接入网签约配置信息之前， 在确定发起连接请求的 MTC设备未存储接入网签约 配置编号和接入网签约配置信息后，通过 RRC信令通知所述 MTC设备对应的接入网签约 配置信息。
27、 如权利要求 24所述的设备， 其特征在于， 所述处理模块还用于：
向需要进行接入网签约配置信息更新的 MTC设备发起寻呼通知 MTC设备读取系统消 息， 并发送包含更新的接入网签约配置信息的系统消息； 或
在所述 MTC设备发起业务请求时， 通过发送包含更新的接入网签约配置信息的专用 信令通知 MTC设备更新对应的接入网签约配置信息。
28、 如权利要求 27 所述的设备， 其特征在于， 所述处理模块根据下列方式确定需要 进行更新的接入网签约配置信息：
在根据收到的来自所述核心网设备的需要进行更新的接入网签约配置信息对应的接 入网签约配置编号后， 确定对应的需要进行更新的接入网签约配置信息。
29、 如权利要求 27所述的设备， 其特征在于， 所述处理模块还用于：
通过专用信令通知 MTC设备更新对应的接入网签约配置信息之前， 在收到来自所述 核心网设备的需要进行更新的接入网签约配置信息对应的接入网签约配置编号后， 确定所 述 MTC设备有更新标记。
30、 如权利要求 29所述的设备， 其特征在于， 所述处理模块还用于：
在更新完成后， 通知所述核心网设备去除所述 MTC设备的更新标记。
31、 如权利要求 26或 28所述的设备， 其特征在于， 所述处理模块还用于： 将来自所述核心网设备的针对所述 MTC设备的接入网签约配置信息对应的内部签约 配置序列号转发给所述 MTC设备。
32、 一种建立连接的核心网设备， 其特征在于， 该核心网设备包括：
处理模块， 用于确定向接入网设备发起连接请求的 MTC设备的接入网签约配置编号； 发送模块， 用于向所述接入网设备发送所述接入网签约配置编号， 用于通知所述接入 网设备根据所述接入网签约配置编号对应的接入网签约配置信息与所述 MTC设备建立连 接。
33、 如权利要求 32所述的设备， 其特征在于， 所述处理模块具体用于：
若所述 MTC设备对应一个接入网签约配置信息， 根据预先设定的设备标识和接入网 签约配置编号的对应关系， 确定所述 MTC设备的设备标识对应的接入网签约配置编号； 若所述 MTC设备对应多个接入网签约配置信息， 根据预先设定的设备标识、 内部签 约配置序列号和接入网签约配置编号的对应关系， 确定所述 MTC设备的设备标识和内部 签约配置序列号对应的接入网签约配置编号。
34、 如权利要求 32或 33所述的设备， 其特征在于， 所述处理模块还用于： 在确定发起连接请求的 MTC设备是签约用户设备后， 确定接入网签约配置编号。
35、 如权利要求 32所述的设备， 其特征在于， 所述处理模块还用于：
在确定向所述接入网设备发起连接请求的 MTC设备未存储接入网签约配置信息后， 根据预先设定的设备标识和接入网签约配置编号的对应关系， 确定所述 MTC设备的设备 标识对应的接入网签约配置编号， 并向所述接入网设备发送确定的接入网签约配置编号， 用于通知所述接入网设备为所述 MTC设备配置所述接入网签约配置编号对应的接入网签 约配置信息； 或根据预先设定的设备标识、 内部签约配置序列号和接入网签约配置编号的 对应关系， 确定所述 MTC设备的设备标识对应的内部签约配置序列号和接入网签约配置 编号， 并向所述接入网设备发送确定的内部签约配置序列号和接入网签约配置编号， 用于 通知所述接入网设备为所述 MTC设备配置所述接入网签约配置编号对应的接入网签约配 置信息和内部签约配置序列号。
36、 如权利要求 32所述的设备， 其特征在于， 所述处理模块还用于：
通知所述接入网设备需要为所述 MTC设备发送更新的接入网签约配置信息对应的接 入网签约配置编号。
37、 如权利要求 36所述的设备， 其特征在于， 所述处理模块还用于：
若所述 MTC设备对应多个接入网签约配置信息，将所述 MTC设备的接入网签约配置 信息对应的内部签约配置序列号发送给所述接入网设备 , 用于通知所述接入网设备将所述 内部签约配置序列号转发给所述 MTC设备。
38、 如权利要求 36所述的设备， 其特征在于， 所述处理模块还用于：
在确定所述 MTC设备有更新标记后，通知所述接入网设备需要为所述 MTC设备发送 更新的接入网签约配置信息对应的接入网签约配置编号。
39、 如权利要求 38所述的设备， 其特征在于， 所述处理模块还用于：
在所述 MTC设备完成接入网签约配置信息的更新后，去除所述 MTC设备的更新标记。
40、 一种建立连接的 MTC设备， 其特征在于， 该 MTC设备包括：
上 莫块， 向接入网设备发起连接请求；
第二建立模块， 用于根据对应的接入网签约配置信息与所述接入网设备建立连接。
41、 如权利要求 40所述的设备， 其特征在于， 所述上报模块具体用于：
若所述 MTC设备对应一个接入网签约配置信息，向接入网设备发起包含所述 MTC设 备的设备标识的连接请求；
若所述 MTC设备对应多个接入网签约配置信息，向接入网设备发起包含所述 MTC设 备的设备标识和建立连接需要使用的接入网签约配置信息对应的内部签约配置序列号的 连接请求。
42、 如权利要求 40 所述的设备， 其特征在于， 所述上报模块预先存储接入网签约配 置信息。
43、 如权利要求 42 所述的设备， 其特征在于， 所述上报模块未存储接入网签约配置 信息；
所述上 莫块还用于：
若所述 MTC设备对应一个接入网签约配置信息， 存储所述接入网设备通知的所述 MTC设备对应的接入网签约配置信息；
若所述 MTC设备对应多个接入网签约配置信息， 根据所述接入网设备通知的所述 MTC设备对应的接入网签约配置信息， 以及每个接入网签约配置信息的顺序，建立并存储 接入网签约配置信息和内部签约配置序列号的对应关系； 或根据所述接入网设备通知的所 述 MTC设备对应的接入网签约配置信息和内部签约配置序列号， 建立并存储接入网签约 配置信息和内部签约配置序列号的对应关系。
44、 如权利要求 40所述的设备， 其特征在于， 所述上报模块还用于：
若所述 MTC设备对应一个接入网签约配置信息， 根据收到的来自所述接入网设备的 需要进行更新的接入网签约配置信息， 更新存储的接入网签约配置信息；
若所述 MTC设备对应多个接入网签约配置信息， 根据收到的来自所述接入网设备的 需要进行更新的接入网签约配置信息和内部签约配置序列号， 更新存储的接入网签约配置 信息和对应的内部签约配置序列号。
45、 一种建立连接的系统， 其特征在于， 该系统包括：
接入网设备 , 用于通过核心网设备确定发起连接请求的 MTC设备的接入网签约配置 编号， 根据预先设定的接入网签约配置编号和接入网签约配置信息的对应关系， 确定所述 MTC设备的接入网签约配置编号对应的接入网签约配置信息，根据确定的接入网签约配置 信息与所述 MTC设备建立连接；
核心网设备， 用于确定向接入网设备发起连接请求的 MTC设备的接入网签约配置编 号， 向所述接入网设备发送所述接入网签约配置编号；
MTC设备，用于向接入网设备发起连接请求，根据对应的接入网签约配置信息与所述 接入网设备建立连接。
PCT/CN2012/080345 2011-10-18 2012-08-20 一种建立连接的方法、系统和设备 WO2013056595A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110317217.1 2011-10-18
CN201110317217.1A CN102368875B (zh) 2011-10-18 2011-10-18 一种建立连接的方法、系统和设备

Publications (1)

Publication Number Publication Date
WO2013056595A1 true WO2013056595A1 (zh) 2013-04-25

Family

ID=45761421

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/080345 WO2013056595A1 (zh) 2011-10-18 2012-08-20 一种建立连接的方法、系统和设备

Country Status (2)

Country Link
CN (1) CN102368875B (zh)
WO (1) WO2013056595A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102368875B (zh) * 2011-10-18 2017-03-01 电信科学技术研究院 一种建立连接的方法、系统和设备
CN104683461B (zh) * 2015-02-15 2019-08-16 青岛海尔智能家电科技有限公司 一种设备配置入网的方法、装置及设备
US20180054796A1 (en) * 2016-08-21 2018-02-22 Qualcomm Incorporated Methods and systems for support of location for the internet of things
US11405863B2 (en) 2016-10-05 2022-08-02 Qualcomm Incorporated Systems and methods to enable combined periodic and triggered location of a mobile device
CN108924876B (zh) * 2017-03-24 2024-05-10 华为技术有限公司 数据传输方法、接入网设备、终端及通信系统
CN108934067B (zh) * 2017-05-25 2020-10-09 华为技术有限公司 一种获取寻呼参数的方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101969635A (zh) * 2010-04-30 2011-02-09 中兴通讯股份有限公司 一种机器通信的接入控制方法及系统和系统
CN102111922A (zh) * 2009-12-25 2011-06-29 中兴通讯股份有限公司 M2m业务签约数据的管理方法及系统、用户签约数据存储器
CN102368875A (zh) * 2011-10-18 2012-03-07 电信科学技术研究院 一种建立连接的方法、系统和设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101730192B (zh) * 2009-02-10 2012-09-05 中兴通讯股份有限公司 接入网策略信息的发送方法、装置及交互系统
CN101895858B (zh) * 2009-05-20 2014-11-05 华为技术有限公司 获取位置更新策略、拒绝位置更新和寻呼的方法和设备
CN102056247B (zh) * 2009-11-10 2014-07-02 中兴通讯股份有限公司 一种限制mtc设备组最大比特率的方法和接入网关
CN102149139B (zh) * 2010-02-10 2016-02-24 中兴通讯股份有限公司 一种mtc系统的上行数据发送方法和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102111922A (zh) * 2009-12-25 2011-06-29 中兴通讯股份有限公司 M2m业务签约数据的管理方法及系统、用户签约数据存储器
CN101969635A (zh) * 2010-04-30 2011-02-09 中兴通讯股份有限公司 一种机器通信的接入控制方法及系统和系统
CN102368875A (zh) * 2011-10-18 2012-03-07 电信科学技术研究院 一种建立连接的方法、系统和设备

Also Published As

Publication number Publication date
CN102368875B (zh) 2017-03-01
CN102368875A (zh) 2012-03-07

Similar Documents

Publication Publication Date Title
US11540100B2 (en) Method and apparatus for communication of terminal in mobile communication system
EP2487944B1 (en) Area-based access control method for terminals which carry out m2m communications in a wireless communication system
TWI748952B (zh) 利用單個連線性上下文支援多個併發服務上下文
US9473877B2 (en) Uplink/downlink transmission method for small amount of data, and corresponding terminal and mobility management unit
US20140237125A1 (en) Method, apparatus, and system for establishing device-to-device connection
WO2012094982A1 (zh) 一种接入控制的方法及装置
WO2013107074A1 (zh) 终端组可及性确定方法及系统
WO2013076455A1 (en) Paging off-line state terminals
WO2013056595A1 (zh) 一种建立连接的方法、系统和设备
WO2011029395A1 (zh) 一种终端的控制方法与装置
WO2017181353A1 (zh) 专用核心网迁移处理方法、设备和系统
CN102857897A (zh) 管理mtc设备的方法、装置及系统
WO2014173152A1 (zh) 终端直接通信的建立方法、服务器、基站和终端
WO2014005551A1 (zh) 用于接近感知的ue配置方法、网络侧设备及系统
EP3086580B1 (en) Accessibility management method and device for m2m terminal/terminal peripheral
CN100576954C (zh) 基于空闲状态用户终端的位置移动能力确定方法及装置
WO2012151846A1 (zh) 一种触发特定位置终端的方法、系统和终端
EP2779778B1 (en) Method and system for effective time control of terminal trigger message
WO2011124173A2 (zh) 网络拥塞处理方法和系统
WO2012151928A1 (zh) 一种触发终端组的方法及系统
WO2012151951A1 (zh) 一种终端触发的方法及系统
WO2013117056A1 (zh) 终端触发方法及装置
WO2013091303A1 (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: 12841210

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

Country of ref document: EP

Kind code of ref document: A1