EP2811767A1 - Control method for the connection between user equipment and network and mobile management equipment - Google Patents
Control method for the connection between user equipment and network and mobile management equipment Download PDFInfo
- Publication number
- EP2811767A1 EP2811767A1 EP13841822.3A EP13841822A EP2811767A1 EP 2811767 A1 EP2811767 A1 EP 2811767A1 EP 13841822 A EP13841822 A EP 13841822A EP 2811767 A1 EP2811767 A1 EP 2811767A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- network
- user equipment
- priority
- connection request
- mobility management
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 230000005540 biological transmission Effects 0.000 claims description 23
- 230000011664 signaling Effects 0.000 claims description 9
- 230000008569 process Effects 0.000 description 24
- 238000004891 communication Methods 0.000 description 21
- 238000010586 diagram Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 15
- 230000009977 dual effect Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 230000001960 triggered effect Effects 0.000 description 6
- 230000005611 electricity Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 238000013475 authorization Methods 0.000 description 4
- 230000007774 longterm Effects 0.000 description 4
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 4
- 101000757159 Manduca sexta Aminopeptidase N Proteins 0.000 description 3
- 206010033799 Paralysis Diseases 0.000 description 3
- 101000889620 Plutella xylostella Aminopeptidase N Proteins 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000000903 blocking effect Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000001186 cumulative effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
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
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/02—Access restriction performed under specific conditions
- H04W48/06—Access restriction performed under specific conditions based on traffic conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
Definitions
- the present invention relates to the field of communications, and in particular, to a method for controlling a connection between a user equipment and a network and a mobility management entity for controlling a connection between a user equipment and a network.
- M2M Machine-to-machine
- 3GPP 3rd Generation Partnership Project
- MTC Machine Type Communications, machine type communications
- the M2M communications is applied to various communications networks, such as the Internet, an industry network, and a communications network. Technologies of machine-to-machine and machine-to-mobile phone data communication and interaction are implemented by sensing and processing application information of devices for M2M communications.
- M2M communications extends a communication range of an existing information and communications network, and by deploying M2M devices having sensing and processing capabilities, information transmission, collaboration, and processing are implemented by means of network facilities, so that various applications such as logistics management, electricity meter reading, and security and health monitoring may conveniently acquire various required information.
- An M2M device does not have a high requirement for real-time quality, so that a single network connection having a low priority is usually established between the M2M device and a network, and a connection between a user equipment and the network cannot be selectively controlled according to an emergency state of actual service data.
- Embodiments of the present invention provide a method for controlling a connection between a user equipment and a network, and a mobility management entity, which can selectively control a connection between a user equipment and a network according to an emergency state of service data.
- a method for controlling a connection between a user equipment and a network includes: receiving, by a mobility management entity, a network connection request sent by a user equipment; determining, by the mobility management entity, a priority of the network connection request and a network overload state; and controlling, by the mobility management entity, a connection between the user equipment and a network according to the priority of the network connection request and the network overload state.
- the controlling, by the mobility management entity, a connection between the user equipment and a network according to the priority of the network connection request and the network overload state includes: rejecting, by the mobility management entity, a network connection request having a low priority according to that the priority of the connection request is the low priority and the network is overloaded, and sending, to the user equipment, a rejecting message carrying a back-off time.
- the method further includes: receiving, by the mobility management entity in the back-off time, a second network connection request sent by the user equipment; and when the mobility management entity determines that a priority of the second network connection request is a non-low priority, sending a timing stop instruction to the user equipment, and controlling establishment of a connection having a non-low priority between the user equipment and the network.
- the controlling, by the mobility management entity, a connection between the user equipment and a network according to the priority of the network connection request and the network overload state includes: when the mobility management entity determines that the priority of the connection request is a low priority or a non-low priority, and determines that the network is not overloaded, controlling establishment of a connection having a corresponding priority between the user equipment and the network.
- the controlling, by the mobility management entity, establishment of a connection having a non-low priority between the user equipment and the network includes: when the mobility management entity determines, according to subscription information of the user equipment, that the user equipment does not belong to a preset user equipment group, controlling establishment of a bearer having a non-low priority or a PDN connection having a non-low priority between the user equipment and the network.
- the controlling a connection between the user equipment and the network includes: when the mobility management entity determines, according to subscription information of the user equipment, that the user equipment belongs to a preset user equipment group, controlling establishment of a public bearer having a non-low priority or a public PDN connection having a non-low priority between the user equipment and the network.
- the controlling a connection between the user equipment and a network according to the priority of the network connection request and the network overload state includes: when the mobility management entity determines that the priority of the network connection request is a non-low priority, and determines that the number of user equipments having established connections having a non-low priority to the network exceeds a limit value, rejecting the connection request having a non-low priority sent by the user equipment.
- the determining, by the mobility management entity, a priority of the network connection request includes: when the mobility management entity determines that the network connection request carries priority information, determining the priority of the network connection request according to the priority information.
- the determining the priority of the network connection request according to the priority information includes: determining, by the mobility management entity, the priority of the network connection request according to a correspondence between an access point name APN and a priority in the priority information.
- the determining, by the mobility management entity, a priority of the network connection request includes: when the mobility management entity determines that the network connection request does not carry priority information, determining that the priority of the network connection request is a non-low priority.
- the determining, by the mobility management entity, a network overload state includes: determining, by the mobility management entity, the network overload state according to an idle state of network resources; and/or determining, by the mobility management entity, the network overload state according to a network overload control command.
- a mobility management entity includes: a transmission module, a determining module, and a control module, where the transmission module receives a network connection request sent by a user equipment; the determining module determines a priority of the network connection request and a network overload state; and the control module controls a connection between the user equipment and a network according to the priority of the network connection request and the network overload state.
- control module controls a connection between the user equipment and a network according to the priority of the network connection request and the network overload state includes: the control module rejects a network connection request having a low priority according to that the priority of the connection request is the low priority and the network is overloaded, and sends, to the user equipment, a rejecting message carrying a back-off time.
- the method further includes: the control module receives, in the back-off time, a second network connection request sent by the user equipment; and when the control module determines that a priority of the second network connection request is a non-low priority, the control module sends a timing stop instruction to the user equipment, and controls establishment of a connection having non-low priority between the user equipment and the network.
- a user equipment includes: a transmission module, a timing module, and a control module, where the transmission module sends a network connection request to a mobility management entity; the transmission module receives a rejecting message which carries a back-off time and is sent by the mobility management entity; the timing module starts a timer according to the back-off time in the rejecting message; and the control module, in the back-off time, forbids the user equipment to send a network connection request having a low priority, and allows the user equipment to send a network connection request having a non-low priority to the mobility management entity.
- the network connection request carries priority information, or does not carry priority information.
- control module controls the user equipment to send the network connection request having a non-low priority to the mobility management entity, further including: the control module stops timing of the timer according to timing stop signaling sent for the network connection request having a non-low priority by the mobility management entity.
- the mobility management entity MME may selectively control the connection between the user equipment and the network by determining the priority of the network connection request and the network overload state.
- communication between M2M devices may be applied to various communications systems, for example, a GSM (Global System for Mobile communication, Global System for Mobile Communications) system, a CDMA (Code Division Multiple Access, Code Division Multiple Access) system, a WCDMA (Wideband Code Division Multiple Access, Wideband Code Division Multiple Access) system, a GPRS (General Packet Radio Service, General Packet Radio Service) system, an LTE (Long Term Evolution, Long Term Evolution) system, an LTE-A (Advanced Long Term Evolution, Advanced Long Term Evolution) system, and the UMTS (Universal Mobile Telecommunications System, Universal Mobile Telecommunications System), which are not limited in the embodiments of the present invention.
- GSM Global System for Mobile communication, Global System for Mobile Communications
- CDMA Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- LTE-A Advanced Long Term Evolution, Advanced Long Term Evolution
- UMTS Universal Mobile Telecommunications System
- FIG. 1 is an application scenario diagram of a communications system according to a first embodiment of the present invention, where a connection between a user equipment and a network is controlled.
- the communications system is described by using an evolved packet system EPS (Evolved Packet System) applied to the 3GPP as an example.
- the evolved packet system EPS includes: an Evolved Universal Terrestrial Radio Access Network (E-UTRAN, Evolved Universal Terrestrial Radio Access Network), a mobility management entity (Mobility Management Entity, MME for short), a serving gateway (Serving Gateway, S-GW for short), a packet data network gateway (Packet Data Network Gateway, P-GW for short), a home subscriber server (Home Subscriber Server, HSS for short), a 3GPP authentication, authorization and accounting (Authentication Authorization and Accounting, AAA for short) server, a policy and charging rules function (Policy and Charging Rules Function, PCRF for short) and other support nodes.
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- MME Mobility Management Entity
- S-GW serving gateway
- P-GW Packet Data Network Gateway
- P-GW Packet Data Network Gateway
- HSS Home
- the MME is responsible for functions, such as mobility management, processing of non-access-stratum (Non-Access-Stratum, NAS for short) signaling, control plane related operations such as management of a user mobility context, reachability management for a mobile terminal in an idle state selected by the P-GW and the S-GW, and selecting of a tracking area list.
- functions such as mobility management, processing of non-access-stratum (Non-Access-Stratum, NAS for short) signaling, control plane related operations such as management of a user mobility context, reachability management for a mobile terminal in an idle state selected by the P-GW and the S-GW, and selecting of a tracking area list.
- the S-GW is an access gateway device and is connected to the E-UTRAN, and functions of the S-GW include: serving as a local anchor point switching between evolved nodeBs (eNodeB, Evolved NodeB), forwarding data between the E-UTRAN and the P-GW, being responsible for caching paging waiting data, lawful interception, data packet routing, and inter-operator accounting based on a user and a quality of service (Quality of Service, Qos for short) class identifier (Qos Class Identifier, QCI for short).
- eNodeB evolved nodeB
- Evolved NodeB evolved nodeB
- Qos for short class identifier
- QCI Quality of Service
- the P-GW is a border gateway between the EPS and a packet data network (Packet Data Network, PDN for short), and functions of the P-GW include: packet filtering, lawful interception, mobile terminal address allocating, and transport layer packet Qos tag that are user-based, service-based uplink and downlink accounting, downlink rate guarantee based on an aggregate maximum bite rate (Aggregate Maximum Bit Bate, AMBR for short), Dynamic Host Configuration Protocol (DHCP v4/v6, Dynamic Host Configuration Protocol v4/v6), and downlink rate guarantee for a cumulative maximum bit rate (Maximum Bit Bate, MBR for short) based on a same guaranteed bit rate (Guaranteed Bit Rate, GBR for short) QCI; in addition, the P-GW is further responsible for binding uplink and downlink bearers.
- Packet Data Network Packet Data Network
- the EPS supports interworking with a non-3GPP system, and the P-GW is used as an anchor point between the 3GPP system and the non-3GPP system.
- the user equipment in the embodiment of the present invention may be an M2M device, for example, a fixed or mobile machine-to-machine communications device such as a temperature tester, or a water/electricity meter.
- M2M device for example, a fixed or mobile machine-to-machine communications device such as a temperature tester, or a water/electricity meter.
- the MME in the embodiment of the present invention controls a connection between a user equipment and a network according to a network connection request of the user equipment, and a specific technical solution is described in the following.
- FIG. 2 is a schematic diagram of a method used by the MME to control the connection between the user equipment and the network according to the first embodiment of the present invention in FIG. 1 .
- Step 210 A mobility management entity MME 20 receives a network connection request sent by a user equipment 10.
- Step 220 The MME 20 determines a priority of the network connection request and a network overload state.
- the MME 20 determines a priority of the network connection request includes:
- FIG. 3 is a schematic diagram of a method used by the user equipment 10 to configure a priority.
- the method used by the user equipment 10 to configure the priority information includes:
- the service data may be meter reading data of a water/electricity meter, temperature/humidity data of a temperature/humidity detector, or the like.
- the priority of the service data includes at least two types of priorities.
- priorities of the service data are a low priority and a non-low priority is used.
- a priority of normal service data is corresponding to service data having a low priority
- a priority of abnormal service data may be corresponding to service data having a non-low priority.
- the user equipment 10 acquires the service data, determines whether a numerical value of the acquired service data exceeds a threshold, and if the numerical value does not exceed the threshold, it is defined that the priority of the service data is a low priority; if the numerical value exceeds the threshold, it is defined that the priority of the service data is a non-low priority.
- the service data is temperature monitoring data of device, and the threshold is predetermined as 40 degrees. If temperature data acquired by the user equipment 10 exceeds 40 degrees, it is determined that the temperature data is abnormal service data, and it is defined that the priority of the abnormal service data is a non-low priority; if the temperature does not exceed 40 degrees, it is determined that the temperature data is normal service data, and it is defined that the priority of the normal service data is a low priority.
- a threshold preset by the user equipment 10 may also be a predetermined range. Further, the user equipment 10 determines whether the numerical value of the acquired service data falls within the predetermined range; if yes, it is determined that the priority of the service data is a low priority; otherwise, it is determined that the priority of the service data is a non-low priority.
- a division manner of the threshold is not limited thereto, and other division manners which can clearly indicate a priority range of the service data are all applicable to the embodiment of the present invention.
- the priority of the service data may also include a low priority and a non-low priority, where the non-low priority may further include a medium priority and a high priority.
- the priority in the embodiment of the present invention is not limited to the low priority and the non-low priority, and the two types of priorities are merely used as an example for description.
- the user equipment 10 may newly add a priority parameter in advance in an attribute of the user equipment 10 according to a user operation.
- the newly added priority parameter is searched for in attribute information of the user equipment 10, and a parameter value corresponding to the priority is configured according to the priority of the service data.
- an M2M device 10 may also add the priority information of the service data in a reserved bit of sent NAS signaling. Corresponding numerical values are set in different idle bits to indicate the priority of the service data.
- the NAS signaling may be the network connection request carrying the priority information, and the priority of the service data is corresponding to the priority of the network connection request.
- the attribute information of the user equipment 10 is an 8-bit binary number, where the 5 th to 8 th bits in the 8 bits are used for indicating the attribute information, and the 1 st to 4 th bits are idle bits.
- the 1 st idle bit in the 1 st to 4 th bits, may be set as the numerical value 1, the 2 nd idle bit may be set as the numerical value 1, the other idle bits are 0, and 0011 indicates that the service data has a characteristic of a dual priority, and the priority of the service data is a non-low priority; or the 1 st idle bit in the 1 st to 4 th bits is set as the numerical value 1, the 2 nd idle bit is set as a numerical value 0, the other idle bits are 0, and 0010 indicates that the service data has a characteristic of a dual priority, and the priority of the service data is a low priority.
- a manner of setting a priority indication in idle bits of the attribute information is not limited thereto, and may include multiple permutations and combinations to indicate the priority information.
- both 1000 and 1100 indicate that the service data has a characteristic of a dual priority, and priorities of the service data are a low priority and a non-low priority separately.
- the priority information may also merely indicate a priority of acquired service data.
- the parameter value 11 indicates that the priority of the service data is a non-low priority
- the parameter value 10 indicates that the priority of the service data is a low priority.
- the reserved bit value 0010 of an attribute message of the user equipment indicates that the priority of the service data is a low priority
- 0011 indicates that the priority of the service data is a non-low priority.
- a type of the network connection request initiated by the user equipment 10 to the MME 20 may be an attach connection request, a PDN connection request, a mobility management message, a session management message, or the like.
- the connection request may carry a user equipment identifier, priority information, and/or a user equipment group identifier.
- the network connection request sent by the user equipment 10 to the MME20 is an attach connection request
- the MME 20 may control establishment of an attach process according to a priority of the attach connection request and the network overload state.
- the MME 20 rejects a connection request having a low priority of the user equipment 10. If the user equipment 10 needs to send service data having a non-low priority, the user equipment 10 needs to establish a network connection having a non-low priority, so that the user equipment 10 may send, to the MME 20, a PDN connection request carrying non-low priority information, and establish the connection having a non-low priority between the user equipment 10 and the network by means of the PDN connection request.
- the MME20 may control, according to a priority of the PDN connection request and the network overload state, the user equipment 10 to establish the connection having a non-low priority to the network.
- that the MME 20 determines the network overload state includes: the MME 20 may determine the network overload state according to an idle state of network resources. For example, if the MME 20 determines that an idle network resource exists, the MME 20 determines that the network is overloaded, if the MME 20 determines that no idle network resource exists, the MME 20 determines that the network is not overloaded.
- the MME 20 may determine the network overload state according to a network overload control command.
- the MME 20 determines that the network overload control command is received, the MME 20 determines that the network is overloaded; if the MME 20 determines that no network overload control command is received, the MME 20 determines that the network is not overloaded.
- the network overload control command can be triggered when a device operator or manufacturer maintains a device or be triggered when a device is faulty.
- the MME 20 rejects the network connection request of the user equipment 10 according to that the priority of the network connection request is a low priority and the network is overloaded, and sends a back-off timer to the user equipment 10.
- FIG. 4 is a schematic diagram of a process in which the MME 20 rejects the network connection request of the user equipment 10.
- the user equipment 10 may activate, according to the rejecting message, the back-off timer to start timing, and the user equipment 10 no longer sends any connection request having a low priority to the MME 20 in the back-off time.
- the MME 20 rejects the network connection request having a low priority sent by the user equipment 10, which can save network resources and protect establishment of a network connection having a non-low priority.
- the MME 20 determines that the priority of the network connection request is a low priority or a non-low priority, and determines that the network is not overloaded, the MME 20 controls the user equipment 10 to establish a network connection having a low priority or a non-low priority.
- the MME 20 determines that the priority of the network connection request is a low priority, and determines that the network is overloaded, the MME 20 rejects the network connection request having a low priority; after the rejecting message carrying the back-off time is sent to the user equipment 10, the MME 20 receives, in the back-off time, a second network connection request sent by the user equipment 10. If the MME 20 determines that a priority of the second network connection request is a non-low priority, the MME 20 sends a timing stop message to the user equipment, and controls the user equipment 10 to establish the connection having a non-low priority to the network.
- a process of establishing a network connection having a non-low priority is used below as an example for description.
- FIG. 5 is a schematic diagram of a process in which the MME 20 controls the user equipment 10 to establish a connection having a non-low priority to the network according to the first embodiment of the present invention.
- the MME 20 controls the user equipment 10 to establish a network connection having a non-low priority. Specifically, step 231 is performed.
- the bearer having a low priority cannot implement transmission of the service data having a non-low priority. Then the user equipment 10 establishes a network connection having a non-low priority by sending a PDN connection request having a non-low priority. Specifically, step 233 is performed, where the attach request or the PDN connection request carries an identifier, and/or priority information, and/or a group identifier of the user equipment 10.
- step 2331 The MME 20 sends a create session request message to an S-GW, where the request message carries public bearer information, such as the group identifier and a public bearer identifier.
- the S-GW determines whether a public bearer has been established for the user equipment group, and if the public bearer has been established, step 2334 is performed; otherwise, a create session request is sent to the P-GW.
- a mapping among an identifier of the user equipment 10 or an IP address of the user equipment 10, a group identifier, a public bearer identifier, an eNodeB TEID, a S-GW TEID and so on is established.
- an uplink data packet is sent to the S-GW by means of the access bearer, then the S-GW finds a corresponding S-GW TEID or public bearer identifier according to the identifier or IP address or group identifier of the user equipment 10, forwards the data to a corresponding public bearer port, and sends the data to the P-GW by means of the public bearer port.
- the public bearer and a default bearer having a non-low priority may transmit service data having a non-low priority, and may also transmit service data having a low priority; each user equipment 10 belonging to the preset user equipment group may transmit the service data by means of the public bearer.
- the MME 20 controls the preset user equipment group to establish a public bearer or a public PDN connection, so that the user equipment 10 belonging to the preset user equipment group may transmit service data having a low priority or a non-low priority by means of the public bearer, or transmit service data having a non-low priority by means of the public PDN connection, which avoids repeatedly establishing a respective bearer or PDN connection for each user equipment 10 belonging to the preset user equipment group, thereby saving network resources.
- step 233 if the MME 20 determines, according to the subscription information of the user equipment 10, that the user equipment 10 does not belong to the preset user equipment group, the MME 20 controls the single user equipment 10 to establish a bearer having a non-low priority or a PDN connection having a non-low priority.
- FIG. 6 is a schematic diagram of controlling the single user equipment 10 to establish a connection having a non-low priority to a network by the MME 20 according to the first embodiment of the present invention.
- a process of establishing a network connection having a non-low priority is described by using an example in which the network connection having a non-low priority is established after a network connection having a low priority is established between the user equipment 10 and the network.
- the single user equipment 10 may also send an attach request having a non-low priority to the MME 20, and if the MME 20 determines that a priority of the attach request is a non-low priority, the MME 20 accepts the attach request, and establishes a network connection having a non-low priority for the user equipment 10.
- the process in which the single user equipment 10 establishes the network connection having a non-low priority or a low priority to the network is similar to the foregoing process in which the preset user equipment group establishes a public bearer or a public PDN connection to the network, which is not described herein again.
- the priority information may further include different APNs (Access Point Name, access point name).
- APNs Access Point Name, access point name.
- the MME 20 identifies connection requests having different priorities according to different APN values. For example, APN1 indicates a connection request having a low priority, and APN2 indicates a connection request having a non-low priority.
- the MME 20 may determine a priority of a connection request according to the APN value.
- the MME 20 may also predefine a limit value for the user equipment 10 that may establish a network connection having a non-low priority.
- the MME 20 determines that user equipment 10 having established the network connections having a non-low priority exceeds the limit value, whether the network is overloaded or not, the MME 20 rejects the connection request having a non-low priority sent by the user equipment 10.
- the MME 20 may further set a limit value for the number of user equipments belonging to the preset user equipment group and establishing connections having a non-low priority to the network.
- the MME 20 determines that the number of the user equipments establishing connections having a non-low priority to the network and in the preset user equipment group exceeds the limit value, the MME 20 rejects the connection request having a non-low priority sent by the user equipment 10.
- the MME 20 protects the network by controlling the number of the user equipments establishing network connections, which avoids network paralysis caused by occupancy of network resources by multiple user equipments unlimitedly establishing network connections having a non-low priority.
- an order in which the MME 20 determines the priority of the network connection request and determines the network overload state is not limited.
- the mobility management entity MME 20 may selectively control the connection between the user equipment 10 and the network by determining the priority of the network connection request and the network overload state.
- FIG. 7 is a schematic structural diagram of a mobility management entity MME 30 that controls a connection between a user equipment and a network according to a second embodiment of the present invention.
- the mobility management entity MME 30 may be applied to a 3GPP evolved packet system EPS (Evolved Packet System), and the evolved packet system EPS includes: an Evolved Universal Terrestrial Radio Access Network (E-UTRAN, Evolved Universal Terrestrial Radio Access Network), a mobility management entity (Mobility Management Entity, MME for short), a serving gateway (Serving Gateway, S-GW for short), a packet data network gateway (Packet Data Network Gateway, P-GW for short), a home subscriber server (Home Subscriber Server, HSS for short), a 3GPP authentication, authorization and accounting (Authentication Authorization and Accounting, AAA for short) server, a policy and charging rules function (Policy and Charging Rules Function, PCRF for short) and other support nodes.
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- MME Mobility Management Entity
- S-GW Serving Gateway
- P-GW Packet Data Network Gateway
- HSS Home Subscriber Server
- AAA Policy and Charging Rules Function
- the MME 30 is responsible for functions, such as mobility management, processing of non-access-stratum (Non-Access-Stratum, NAS for short) signaling, control plane related operations such as management of a user mobility context, reachability management for a mobile terminal in an idle state selected by the P-GW and the S-GW, and selecting of a tracking area list.
- functions such as mobility management, processing of non-access-stratum (Non-Access-Stratum, NAS for short) signaling, control plane related operations such as management of a user mobility context, reachability management for a mobile terminal in an idle state selected by the P-GW and the S-GW, and selecting of a tracking area list.
- the mobility management entity MME 30 includes a transceiver 31 and a processor 32.
- the transceiver 31 receives a network connection request sent by a user equipment 10; the processor 32 determines a priority of the network connection request and a network overload state, and further controls a connection between the user equipment 10 and a network according to the priority of the network connection request and the network overload state.
- the mobility management entity MME 30 may selectively control the connection between the user equipment 10 and the network by determining the priority of the network connection request and the network overload state.
- the transceiver 31 is configured to receive and send information in an information receiving and sending process or a call process, and the transceiver 31 may communicate with other devices by using a wireless communications system and the network. According to the embodiment of the present invention, the transceiver 31 receives the network connection request sent by the user equipment 10, and sends, according to the priority of the network connection request and the network overload state, information about controlling establishment of the connection between the user equipment 10 and the network.
- That the processor 32 determines a priority of the network connection request includes: the processor 32 determines whether priority information is carried in the network connection request; and if priority information is carried, the priority of the network connection request is determined according to the priority information; if the priority information is not carried, it is determined that the priority of the network connection request is a non-low priority.
- the priority information is preconfigured in the user equipment 10, and a configuration process of the priority is based on the first embodiment and similar to the process of configuring the priority information described in FIG. 3 .
- processor 32 determines the network overload state includes: the processor 32 may determine the network overload state according to an idle state of network resources.
- the processor 32 determines that an idle network resource exists, the processor 32 determines that the network is overloaded; if the processor 32 determines that no idle network resource exists, the processor 32 determines that the network is not overloaded.
- the processor 32 may determine the network overload state according to a network overload control command.
- the processor 32 determines that the network overload control command is received, the processor 32 determines that the network is overloaded; if the processor 32 determines that no network overload control command is received, the processor 32 determines that the network is not overloaded.
- the network overload control command can be triggered when a device operator or manufacturer maintains a device or be triggered when a device is faulty.
- the processor 32 controls a connection between the user equipment 10 and a network according to the priority of the network connection request and the network overload state includes:
- the MME 20 controls the user equipment 10 to establish a network connection having a low priority or a non-low priority.
- the processor 32 determines that the priority of the network connection request is a low priority, determines that the network is overloaded, rejects the network connection request having a low priority, and sends, to the user equipment 10, the rejecting message carrying the back-off time
- the processor 32 in the back-off time, receives a second network connection request sent by the user equipment 10, sends a timing stop message to the user equipment 10 if it is determined that a priority of the second network connection request is a non-low priority, and controls establishment of a connection having a non-low priority between the user equipment 10 and the network.
- the processor 32 determines that the user equipment 10 meets a condition of establishing the connection having a non-low priority to the network, that the controlling establishment of a connection having a non-low priority between the user equipment 10 and the network includes:
- the processor 32 determines, according to subscription information of the user equipment 10, that the user equipment 10 does not belong to a preset user equipment group, the processor 32 controls the user equipment 10 to establish a single bearer having a non-low priority or a single PDN connection having a non-low priority to the network.
- the process in which the processor 32 controls the user equipment 10 to establish a network connection is similar to that in the first embodiment, and is not described herein again.
- the priority information may further include different APNs (Access Point Name, access point name).
- the processor 32 identifies connection requests having different priorities according to different APN values. For example, APN1 indicates a connection request having a low priority, and APN2 indicates a connection request having a non-low priority.
- the processor 32 may determine a priority of a connection request according to the APN value.
- the processor 32 may also predefine a limit value for the user equipment 10 that may establish a network connection having a non-low priority.
- the processor 32 determines that the user equipment 10 establishing the network connection having a non-low priority exceeds the limit value, whether the network is overloaded or not, the processor 32 rejects the connection request having a non-low priority sent by the user equipment 10.
- the processor 32 may further set a limit value for the number of user equipments belonging to the preset user equipment group and establishing connections having a non-low priority to the network.
- the processor 32 determines that the number of the user equipments establishing connections having a non-low priority to the network and in the preset user equipment group exceeds the limit value, the processor 32 rejects the connection request having a non-low priority sent by the user equipment 10.
- the processor 32 protects the network by controlling the number of the user equipments establishing network connections, which avoids network paralysis caused by occupancy of network resources by unlimitedly establishing the network connections having a non-low priority by multiple user equipments.
- an order in which the processor 32 determines the priority of the network connection request and determines the network overload state is not limited.
- the MME 30 may further include a memory 34, and the memory 34 may be configured to store an uplink control instruction or data information sent by an M2M, and store uplink and downlink control signaling and data information between the MME 30 and the S-GW or between the MME 30 and the P-GW.
- the memory 34 may be integrated with the HSS.
- the mobility management entity MME 40 may selectively control the connection between the user equipment 10 and the network by determining the priority of the network connection request and the network overload state.
- FIG. 8 is a schematic diagram of a mobility management entity that controls a connection between a user equipment and a network according to a third embodiment of the present invention.
- a mobility management entity 40 includes a transmission module 41, a determining module 43, and a control module 45.
- the transmission module 41 receives a network connection request sent by a user equipment 10.
- the determining module 43 determines a priority of the network connection request and a network overload state.
- the control module 45 controls a connection between the user equipment 10 and the network according to the priority of the network connection request and the network overload state.
- the mobility management entity MME 40 may selectively control the connection between the user equipment 10 and the network by determining the priority of the network connection request and the network overload state.
- the transmission module 41 receives a network connection request which carries priority information sent by the user equipment 10, where the priority information indicates the priority of the network connection request; or receives a network connection request which does not carry priority information and is sent by the user equipment 10.
- the priority information may indicate that the priority of the network connection request is a low priority or a non-low priority.
- the non-low priority may further include multiple levels, such as a medium priority and a high priority.
- the priority information is preconfigured in the user equipment 10, and a configuration process of the priority is based on the first embodiment and similar to the process of configuring the priority information described in FIG. 3 .
- That the determining module 43 determines a priority of the network connection request includes:
- determining module 43 determines the network overload state includes:
- the determining module 43 determines that an idle network resource exists, the determining module 43 determines that the network is overloaded; if the determining module 43 determines that no idle network resource exists, the determining module 43 determines that the network is not overloaded.
- the determining module 43 may determine the network overload state according to a network overload control command.
- the determining module 43 determines that the network overload control command is received, the determining module 43 determines that the network is overloaded; if the determining module 43 determines that no network overload control command is received, the determining module 43 determines that the network is not overloaded.
- the network overload control command can be triggered when a device operator or manufacturer maintains a device or be triggered when a device is faulty.
- control module 45 controls a connection between the user equipment 10 and the network according to the priority of the network connection request and the network overload state includes:
- control module 45 determines that the priority of the network connection request is a low priority or a non-low priority, and determines that the network is not overloaded, the control module 45 controls the user equipment 10 to establish a network connection with a low priority or a non-low priority.
- control module 45 determines that the priority of the network connection request is a low priority, determines that the network is overloaded, rejects the network connection request having a low priority and sends, to the user equipment 10, the rejecting message carrying the back-off time
- the control module 45 in the back-off time, receives a second network connection request sent by the user equipment 10; sends a timing stop message to the user equipment 10 if it is determined that a priority of the second network connection request is a non-low priority, the control module 45, and controls establishment of a connection having a non-low priority between the user equipment 10 and the network.
- control module 45 determines that the user equipment 10 meets a condition of establishing the connection having a non-low priority to the network, that the controlling establishment of a connection having a non-low priority between the user equipment 10 and the network includes:
- control module 45 determines, according to subscription information of the user equipment 10, that the user equipment 10 does not belong to a preset user equipment group, the control module 45 controls the user equipment 10 to establish a single bearer having a non-low priority or a single PDN connection having a non-low priority to the network.
- the process in which the control module 45 controls the user equipment 10 to establish a network connection is similar to that in the first embodiment, and is not described herein again.
- the priority information may further include different APNs (Access Point Name, access point name).
- the control module 45 identifies connection requests having different priorities according to different APN values. For example, APN1 indicates a connection request having a low priority, and APN2 indicates a connection request having a non-low priority. The control module 45 may determine a priority of a connection request according to the APN value.
- control module 45 may also predefine a limit value for the user equipment 10 that may establish a network connection having a non-low priority.
- the control module 45 determines that the user equipment 10 establishing the network connection having a non-low priority exceeds the limit value, whether the network is overloaded or not, the control module 45 rejects the connection request having a non-low priority sent by the user equipment 10.
- control module 45 determines the priority of the network connection request and determines the network overload state is not limited.
- the mobility management entity MME 40 may selectively control the connection between the user equipment 10 and the network by determining the priority of the network connection request and the network overload state.
- FIG. 9 is a structural diagram of a user equipment 50 that controls a connection to a network according to a fourth embodiment of the present invention.
- the user equipment 50in the embodiment of the present invention may be an M2M device, for example, a fixed or mobile machine-to-machine communications device such as a temperature tester, or a water/electricity meter.
- the user equipment 50 includes a transmission module 52, a timing module 53, and a control module 54, where:
- the user equipment 50 in the embodiment of the present invention according to the rejecting message sent by the mobility management entity 60, forbids the user equipment 50 to send the network connection request having a low priority, and allows the user equipment 50 to send the network connection request having a non-low priority, which prevents the user equipment 50 from continuously sending network connection requests having a low priority to a network, and avoids blocking the network.
- That the transmission module 52 sends a network connection request to a mobility management entity 60 includes: the transmission module 52 may send, to the mobility management entity 60, a network connection request which carries priority information, or send, to the mobility management entity 60, a network connection request which does not carry priority information.
- the mobility management entity 60 may determine that the default priority of the network connection request is a non-low priority.
- the control module 54 controls the user equipment 50 to send a network connection request having a non-low priority to the mobility management entity 60, and stops timing of the timer according to timing stop signaling sent for the network connection request having a non-low priority by the mobility management entity 60.
- the user equipment 50 in the embodiment of the present invention may further include a detection module 55, a determining module 56, and a configuration module 57, where the detection module 55 is configured to detect and acquire service data, such as temperature data and water/electricity data.
- the determining module 56 determines a priority of the service data acquired by the detection module.
- the configuration module 57 configures priority information corresponding to the priority of the service data.
- the user equipment 50 in the embodiment of the present invention according to the rejecting message sent by the mobility management entity 60, forbids the user equipment 50 to send network connection request having a low priority, and allows the user equipment 50 to send network connection request having a non-low priority, which prevents the user equipment 50 from continuously sending network connection requests having a low priority to a network, and avoids blocking the network.
- FIG. 10 is a flowchart of a method for controlling a connection between a user equipment and a network according to a fifth embodiment of the present invention.
- the method for controlling the connection between the user equipment 50 and the network includes:
- the user equipment 50 is, according to the rejecting message sent by the mobility management entity 60, forbidden to send the network connection request having a low priority, and allowed to send the network connection request having a non-low priority, which prevents the user equipment 50 from continuously sending network connection requests having a low priority to a network, and avoids blocking the network.
- the user equipment 50 may send, to the mobility management entity 60, a network connection request which carries priority information, or send, to the mobility management entity 60, a network connection request which does not carry priority information.
- step 104 that the user equipment 50 is allowed to send the network connection request having a non-low priority to the mobility management entity 60 in the back-off time includes:
- the method further includes: the user equipment 50 stops timing of the timer according to timing stop signaling sent for the network connection request having a non-low priority by the mobility management entity 60.
- the user equipment 50 is, according to the rejecting message sent by the mobility management entity 60, forbidden to send the network connection request having a low priority, and allowed to send the network connection request having a non-low priority, which may selectively control the connection between the user equipment and the network.
- various function modules in the embodiments of the present invention may be integrated in one processing device, or modules may exist physically independently, or two or more than two modules may be integrated in one device.
- the function When the function is implemented in a software function device form and is sold or used as an independent product, the function may be stored in a computer readable storage medium. Based on such an understanding, the technical solutions of the present invention essentially, or the part contributing to the prior art, or a part of the technical solutions may be implemented in a form of a software product.
- the computer software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or a part of the steps of the methods described in the embodiments of the present invention.
- the foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.
- program code such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- This application claims priority to Chinese Patent Application No.
201210370562.6 - The present invention relates to the field of communications, and in particular, to a method for controlling a connection between a user equipment and a network and a mobility management entity for controlling a connection between a user equipment and a network.
- With the development of 3rd-generation mobile communications (3rd-generation, 3G) technologies, application in M2M (Machine-to-Machine, machine-to-machine) communications becomes extensive. A corresponding name of M2M in a 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) system is MTC (Machine Type Communications, machine type communications), which is a short name of machine-to-machine communications. The M2M communications is applied to various communications networks, such as the Internet, an industry network, and a communications network. Technologies of machine-to-machine and machine-to-mobile phone data communication and interaction are implemented by sensing and processing application information of devices for M2M communications. M2M communications extends a communication range of an existing information and communications network, and by deploying M2M devices having sensing and processing capabilities, information transmission, collaboration, and processing are implemented by means of network facilities, so that various applications such as logistics management, electricity meter reading, and security and health monitoring may conveniently acquire various required information.
- An M2M device does not have a high requirement for real-time quality, so that a single network connection having a low priority is usually established between the M2M device and a network, and a connection between a user equipment and the network cannot be selectively controlled according to an emergency state of actual service data.
- Embodiments of the present invention provide a method for controlling a connection between a user equipment and a network, and a mobility management entity, which can selectively control a connection between a user equipment and a network according to an emergency state of service data.
- According to a first aspect, a method for controlling a connection between a user equipment and a network is provided, and includes: receiving, by a mobility management entity, a network connection request sent by a user equipment; determining, by the mobility management entity, a priority of the network connection request and a network overload state; and controlling, by the mobility management entity, a connection between the user equipment and a network according to the priority of the network connection request and the network overload state.
- In a first possible implementation manner of the first aspect, the controlling, by the mobility management entity, a connection between the user equipment and a network according to the priority of the network connection request and the network overload state includes: rejecting, by the mobility management entity, a network connection request having a low priority according to that the priority of the connection request is the low priority and the network is overloaded, and sending, to the user equipment, a rejecting message carrying a back-off time.
- With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, after the sending, by the mobility management entity to the user equipment, a rejecting message carrying a back-off time, the method further includes: receiving, by the mobility management entity in the back-off time, a second network connection request sent by the user equipment; and when the mobility management entity determines that a priority of the second network connection request is a non-low priority, sending a timing stop instruction to the user equipment, and controlling establishment of a connection having a non-low priority between the user equipment and the network.
- In a third possible implementation manner of the first aspect, the controlling, by the mobility management entity, a connection between the user equipment and a network according to the priority of the network connection request and the network overload state includes: when the mobility management entity determines that the priority of the connection request is a low priority or a non-low priority, and determines that the network is not overloaded, controlling establishment of a connection having a corresponding priority between the user equipment and the network.
- With reference to the second possible implementation manner or the third possible implementation manner of the first aspect, in a fourth possible implementation manner, the controlling, by the mobility management entity, establishment of a connection having a non-low priority between the user equipment and the network includes: when the mobility management entity determines, according to subscription information of the user equipment, that the user equipment does not belong to a preset user equipment group, controlling establishment of a bearer having a non-low priority or a PDN connection having a non-low priority between the user equipment and the network.
- With reference to the second possible implementation manner or the third possible implementation manner of the first aspect, in a fifth possible implementation manner, the controlling a connection between the user equipment and the network includes: when the mobility management entity determines, according to subscription information of the user equipment, that the user equipment belongs to a preset user equipment group, controlling establishment of a public bearer having a non-low priority or a public PDN connection having a non-low priority between the user equipment and the network.
- With reference to the first aspect or any one of the foregoing possible implementation manners, in a sixth possible implementation manner, the controlling a connection between the user equipment and a network according to the priority of the network connection request and the network overload state includes: when the mobility management entity determines that the priority of the network connection request is a non-low priority, and determines that the number of user equipments having established connections having a non-low priority to the network exceeds a limit value, rejecting the connection request having a non-low priority sent by the user equipment.
- With reference to the first aspect or any one of the foregoing possible implementation manners, in a seventh possible implementation manner, the determining, by the mobility management entity, a priority of the network connection request includes: when the mobility management entity determines that the network connection request carries priority information, determining the priority of the network connection request according to the priority information.
- With reference to the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner, the determining the priority of the network connection request according to the priority information includes: determining, by the mobility management entity, the priority of the network connection request according to a correspondence between an access point name APN and a priority in the priority information.
- With reference to any one of the first to seventh possible implementation manners of the first aspect, in a ninth possible implementation manner, the determining, by the mobility management entity, a priority of the network connection request includes: when the mobility management entity determines that the network connection request does not carry priority information, determining that the priority of the network connection request is a non-low priority.
- With reference to the first aspect or any one of the foregoing possible implementation manners, in a tenth possible implementation manner, the determining, by the mobility management entity, a network overload state includes: determining, by the mobility management entity, the network overload state according to an idle state of network resources; and/or determining, by the mobility management entity, the network overload state according to a network overload control command.
- According to a second aspect, a mobility management entity is provided, and includes: a transmission module, a determining module, and a control module, where the transmission module receives a network connection request sent by a user equipment; the determining module determines a priority of the network connection request and a network overload state; and the control module controls a connection between the user equipment and a network according to the priority of the network connection request and the network overload state.
- In a first possible implementation manner of the second aspect, that the control module controls a connection between the user equipment and a network according to the priority of the network connection request and the network overload state includes: the control module rejects a network connection request having a low priority according to that the priority of the connection request is the low priority and the network is overloaded, and sends, to the user equipment, a rejecting message carrying a back-off time.
- With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, after the control module sends, to the user equipment, a rejecting message carrying the back-off time, the method further includes: the control module receives, in the back-off time, a second network connection request sent by the user equipment; and when the control module determines that a priority of the second network connection request is a non-low priority, the control module sends a timing stop instruction to the user equipment, and controls establishment of a connection having non-low priority between the user equipment and the network.
- According to a third aspect, a user equipment is provided, and includes: a transmission module, a timing module, and a control module, where the transmission module sends a network connection request to a mobility management entity; the transmission module receives a rejecting message which carries a back-off time and is sent by the mobility management entity; the timing module starts a timer according to the back-off time in the rejecting message; and the control module, in the back-off time, forbids the user equipment to send a network connection request having a low priority, and allows the user equipment to send a network connection request having a non-low priority to the mobility management entity.
- In a first possible implementation manner of the third aspect, the network connection request carries priority information, or does not carry priority information.
- With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, that the control module allows, in the back-off time, the network connection request having a non-low priority to be sent to the mobility management entity includes: the control module controls, in the back-off time, the user equipment to send the network connection request having a non-low priority to the mobility management entity when the user equipment acquires service data having a non-low priority.
- With reference to the second possible implementation manner of the third aspect, in a third possible implementation manner, after the control module controls the user equipment to send the network connection request having a non-low priority to the mobility management entity, further including: the control module stops timing of the timer according to timing stop signaling sent for the network connection request having a non-low priority by the mobility management entity.
- According to the embodiments of the present invention, the mobility management entity MME may selectively control the connection between the user equipment and the network by determining the priority of the network connection request and the network overload state.
- To describe the technical solutions in the embodiments of the present invention or in the prior art more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.
-
FIG. 1 is an application scenario diagram of a communications system according to a first embodiment of the present invention, where a mobility management entity MME controls a connection between a user equipment and a network; -
FIG. 2 is a schematic diagram of a method used by the MME to control the connection between the user equipment and the network according to the first embodiment of the present invention inFIG. 1 ; -
FIG. 3 is a schematic diagram of a method for configuring priority information according to the first embodiment of the present invention; -
FIG. 4 is a schematic diagram of a process in which the MME rejects a network connection request of the user equipment according to the first embodiment of the present invention; -
FIG. 5 is a schematic diagram of a process in which the MME controls a preset user equipment group to establish a connection having a non-low priority to a network according to the first embodiment of the present invention; -
FIG. 6 is a schematic diagram of controlling a single user equipment to establish a PDN connection having a non-low priority to a network by the MME according to the first embodiment of the present invention; -
FIG. 7 is a schematic structural diagram of a mobility management entity MME that controls a connection between a user equipment and a network according to a second embodiment of the present invention; -
FIG. 8 is a schematic diagram of a mobility management entity that controls a connection between a user equipment and a network according to a third embodiment of the present invention; -
FIG. 9 is a structural diagram of a user equipment that controls a connection to a network according to a fourth embodiment of the present invention; and -
FIG. 10 is a flowchart of a method for controlling a connection between a user equipment and a network according to a fifth embodiment of the present invention. - The following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are a part rather than all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.
- It should be understood that, communication between M2M devices according to the embodiments of the present invention may be applied to various communications systems, for example, a GSM (Global System for Mobile communication, Global System for Mobile Communications) system, a CDMA (Code Division Multiple Access, Code Division Multiple Access) system, a WCDMA (Wideband Code Division Multiple Access, Wideband Code Division Multiple Access) system, a GPRS (General Packet Radio Service, General Packet Radio Service) system, an LTE (Long Term Evolution, Long Term Evolution) system, an LTE-A (Advanced Long Term Evolution, Advanced Long Term Evolution) system, and the UMTS (Universal Mobile Telecommunications System, Universal Mobile Telecommunications System), which are not limited in the embodiments of the present invention.
-
FIG. 1 is an application scenario diagram of a communications system according to a first embodiment of the present invention, where a connection between a user equipment and a network is controlled. - As shown in
FIG. 1 , the communications system according to the embodiment of the present invention is described by using an evolved packet system EPS (Evolved Packet System) applied to the 3GPP as an example. The evolved packet system EPS includes: an Evolved Universal Terrestrial Radio Access Network (E-UTRAN, Evolved Universal Terrestrial Radio Access Network), a mobility management entity (Mobility Management Entity, MME for short), a serving gateway (Serving Gateway, S-GW for short), a packet data network gateway (Packet Data Network Gateway, P-GW for short), a home subscriber server (Home Subscriber Server, HSS for short), a 3GPP authentication, authorization and accounting (Authentication Authorization and Accounting, AAA for short) server, a policy and charging rules function (Policy and Charging Rules Function, PCRF for short) and other support nodes. - The MME is responsible for functions, such as mobility management, processing of non-access-stratum (Non-Access-Stratum, NAS for short) signaling, control plane related operations such as management of a user mobility context, reachability management for a mobile terminal in an idle state selected by the P-GW and the S-GW, and selecting of a tracking area list.
- The S-GW is an access gateway device and is connected to the E-UTRAN, and functions of the S-GW include: serving as a local anchor point switching between evolved nodeBs (eNodeB, Evolved NodeB), forwarding data between the E-UTRAN and the P-GW, being responsible for caching paging waiting data, lawful interception, data packet routing, and inter-operator accounting based on a user and a quality of service (Quality of Service, Qos for short) class identifier (Qos Class Identifier, QCI for short).
- The P-GW is a border gateway between the EPS and a packet data network (Packet Data Network, PDN for short), and functions of the P-GW include: packet filtering, lawful interception, mobile terminal address allocating, and transport layer packet Qos tag that are user-based, service-based uplink and downlink accounting, downlink rate guarantee based on an aggregate maximum bite rate (Aggregate Maximum Bit Bate, AMBR for short), Dynamic Host Configuration Protocol (DHCP v4/v6, Dynamic Host Configuration Protocol v4/v6), and downlink rate guarantee for a cumulative maximum bit rate (Maximum Bit Bate, MBR for short) based on a same guaranteed bit rate (Guaranteed Bit Rate, GBR for short) QCI; in addition, the P-GW is further responsible for binding uplink and downlink bearers.
- The EPS supports interworking with a non-3GPP system, and the P-GW is used as an anchor point between the 3GPP system and the non-3GPP system.
- The user equipment in the embodiment of the present invention may be an M2M device, for example, a fixed or mobile machine-to-machine communications device such as a temperature tester, or a water/electricity meter.
- The MME in the embodiment of the present invention controls a connection between a user equipment and a network according to a network connection request of the user equipment, and a specific technical solution is described in the following.
-
FIG. 2 is a schematic diagram of a method used by the MME to control the connection between the user equipment and the network according to the first embodiment of the present invention inFIG. 1 . - Step 210: A mobility management entity MME 20 receives a network connection request sent by a
user equipment 10. - Step 220: The
MME 20 determines a priority of the network connection request and a network overload state. - Specifically, that the
MME 20 determines a priority of the network connection request includes: - the
MME 20 determines whether the network connection request carries priority information; and if priority information is carried, the priority of the network connection request is determined according to the priority information; if the priority information is not carried, it is determined that the priority of the network connection request is a non-low priority. - The priority information is preconfigured in the
user equipment 10. Referring toFIG. 3, FIG. 3 is a schematic diagram of a method used by theuser equipment 10 to configure a priority. - The method used by the
user equipment 10 to configure the priority information includes: - Step 2201: The
user equipment 10 acquires service data, and determines a priority of the service data. - It can be understood that, the service data may be meter reading data of a water/electricity meter, temperature/humidity data of a temperature/humidity detector, or the like.
- In this embodiment, the priority of the service data includes at least two types of priorities. An example in which priorities of the service data are a low priority and a non-low priority is used. For example, a priority of normal service data is corresponding to service data having a low priority, and a priority of abnormal service data may be corresponding to service data having a non-low priority.
- Specifically, the
user equipment 10 acquires the service data, determines whether a numerical value of the acquired service data exceeds a threshold, and if the numerical value does not exceed the threshold, it is defined that the priority of the service data is a low priority; if the numerical value exceeds the threshold, it is defined that the priority of the service data is a non-low priority. - For example, the service data is temperature monitoring data of device, and the threshold is predetermined as 40 degrees. If temperature data acquired by the
user equipment 10 exceeds 40 degrees, it is determined that the temperature data is abnormal service data, and it is defined that the priority of the abnormal service data is a non-low priority; if the temperature does not exceed 40 degrees, it is determined that the temperature data is normal service data, and it is defined that the priority of the normal service data is a low priority. - It can be understood that, a threshold preset by the
user equipment 10 may also be a predetermined range. Further, theuser equipment 10 determines whether the numerical value of the acquired service data falls within the predetermined range; if yes, it is determined that the priority of the service data is a low priority; otherwise, it is determined that the priority of the service data is a non-low priority. In the embodiment of the present invention, a division manner of the threshold is not limited thereto, and other division manners which can clearly indicate a priority range of the service data are all applicable to the embodiment of the present invention. - It can be understood that, the priority of the service data may also include a low priority and a non-low priority, where the non-low priority may further include a medium priority and a high priority. For setting a priority level, multiple levels may be set according to actual needs. The priority in the embodiment of the present invention is not limited to the low priority and the non-low priority, and the two types of priorities are merely used as an example for description.
- Step 2202: The
user equipment 10 configures, according to the priority of the service data, the priority information corresponding to the service data. - Specifically, an example in which the priority of the service data has a dual priority is used. The
user equipment 10 may newly add a priority parameter in advance in an attribute of theuser equipment 10 according to a user operation. In this embodiment, after theuser equipment 10 acquires the service data, the newly added priority parameter is searched for in attribute information of theuser equipment 10, and a parameter value corresponding to the priority is configured according to the priority of the service data. As shown in Table 1, for example, if the parameter value is 11, 1 in the tens digit place indicates that the service data is service data having a dual priority, and 1 in the ones digit place indicates the priority of the service data is a non-low priority; if the parameter value is 10, 1 in the tens digit place indicates that the service data is service data having a dual priority, and 0 in the ones digit place indicates that the priority of the service data is a low priority.Table 1 Newly added priority parameter Parameter value Descriptions Dual Priority 11 Non-low priority of a dual priority Dual Priority 10 Low priority of a dual priority - Optionally, an
M2M device 10 may also add the priority information of the service data in a reserved bit of sent NAS signaling. Corresponding numerical values are set in different idle bits to indicate the priority of the service data. For a method for setting the priority, refer to Table 2 to Table 3. The NAS signaling may be the network connection request carrying the priority information, and the priority of the service data is corresponding to the priority of the network connection request.Table 2 8 7 6 5 4 3 2 1 Attribute information bits 0 Idle bit 0 Idle bit 1 Idle bit 1 Idle bit Table 3 8 7 6 5 4 3 2 1 Attribute information bits 0 Idle bit 0 Idle bit 1 Idle bit 0 Idle bit - As shown in Table 2 to Table 3, for example, the attribute information of the
user equipment 10 is an 8-bit binary number, where the 5th to 8th bits in the 8 bits are used for indicating the attribute information, and the 1st to 4th bits are idle bits. In the embodiment of the present invention, in the 1st to 4th bits, the 1st idle bit may be set as the numerical value 1, the 2nd idle bit may be set as the numerical value 1, the other idle bits are 0, and 0011 indicates that the service data has a characteristic of a dual priority, and the priority of the service data is a non-low priority; or the 1st idle bit in the 1st to 4th bits is set as the numerical value 1, the 2nd idle bit is set as a numerical value 0, the other idle bits are 0, and 0010 indicates that the service data has a characteristic of a dual priority, and the priority of the service data is a low priority. - It can be understood that, a manner of setting a priority indication in idle bits of the attribute information is not limited thereto, and may include multiple permutations and combinations to indicate the priority information. For example, both 1000 and 1100 indicate that the service data has a characteristic of a dual priority, and priorities of the service data are a low priority and a non-low priority separately.
- It can be further understood that, the priority information may also merely indicate a priority of acquired service data. For example, in Table 1, the parameter value 11 indicates that the priority of the service data is a non-low priority, and the
parameter value 10 indicates that the priority of the service data is a low priority. In Table 2 to Table 3, the reserved bit value 0010 of an attribute message of the user equipment indicates that the priority of the service data is a low priority, and 0011 indicates that the priority of the service data is a non-low priority. - Step 2203: The
user equipment 10 sends, to theMME 20, a network connection request which carries the priority information or does not carry the priority information. - In this embodiment, a type of the network connection request initiated by the
user equipment 10 to theMME 20 may be an attach connection request, a PDN connection request, a mobility management message, a session management message, or the like. The connection request may carry a user equipment identifier, priority information, and/or a user equipment group identifier. - When the
user equipment 10 is used for the first time, the network connection request sent by theuser equipment 10 to the MME20 is an attach connection request, and theMME 20 may control establishment of an attach process according to a priority of the attach connection request and the network overload state. - When the
user equipment 10 is not used for the first time, that is, theuser equipment 10 completes an attach process having a low priority with a network and establishes a connection having a low priority to the network, when the network is overloaded, theMME 20 rejects a connection request having a low priority of theuser equipment 10. If theuser equipment 10 needs to send service data having a non-low priority, theuser equipment 10 needs to establish a network connection having a non-low priority, so that theuser equipment 10 may send, to theMME 20, a PDN connection request carrying non-low priority information, and establish the connection having a non-low priority between theuser equipment 10 and the network by means of the PDN connection request. When the connection request sent by theuser equipment 10 to the MME20 is a PDN connection request carrying low priority information, the MME20 may control, according to a priority of the PDN connection request and the network overload state, theuser equipment 10 to establish the connection having a non-low priority to the network. - Optionally or further, that the
MME 20 determines the network overload state includes: theMME 20 may determine the network overload state according to an idle state of network resources. For example, if theMME 20 determines that an idle network resource exists, theMME 20 determines that the network is overloaded, if theMME 20 determines that no idle network resource exists, theMME 20 determines that the network is not overloaded. - Optionally, the
MME 20 may determine the network overload state according to a network overload control command. - For example, if the
MME 20 determines that the network overload control command is received, theMME 20 determines that the network is overloaded; if theMME 20 determines that no network overload control command is received, theMME 20 determines that the network is not overloaded. - It can be understood that, the network overload control command can be triggered when a device operator or manufacturer maintains a device or be triggered when a device is faulty.
- Step 230: The
MME 20 controls a connection between theM2M device 10 and the network according to the priority of the network connection request and the network overload state. - Specifically, the
MME 20 rejects the network connection request of theuser equipment 10 according to that the priority of the network connection request is a low priority and the network is overloaded, and sends a back-off timer to theuser equipment 10. - For example, as shown in
FIG. 4, FIG. 4 is a schematic diagram of a process in which theMME 20 rejects the network connection request of theuser equipment 10. - Step 241: The
MME 20 receives the network connection request sent by theuser equipment 10. - Step 242: If the
MME 20 determines that the priority of the connection request is a low priority, and determines that the network is overloaded, theMME 20 rejects the connection request having a low priority, and sends, to theuser equipment 10, a rejecting message carrying a back-off time. - Step 243: The
MME 20 does not receive, in the back-off time, any network connection request having a low priority sent by theuser equipment 10. - Optionally, the
user equipment 10 may activate, according to the rejecting message, the back-off timer to start timing, and theuser equipment 10 no longer sends any connection request having a low priority to theMME 20 in the back-off time. - In this embodiment, under the circumstance that the network is overloaded, the
MME 20 rejects the network connection request having a low priority sent by theuser equipment 10, which can save network resources and protect establishment of a network connection having a non-low priority. - Optionally, when the
MME 20 determines that the priority of the network connection request is a low priority or a non-low priority, and determines that the network is not overloaded, theMME 20 controls theuser equipment 10 to establish a network connection having a low priority or a non-low priority. - Optionally, when the
MME 20 determines that the priority of the network connection request is a low priority, and determines that the network is overloaded, theMME 20 rejects the network connection request having a low priority; after the rejecting message carrying the back-off time is sent to theuser equipment 10, theMME 20 receives, in the back-off time, a second network connection request sent by theuser equipment 10. If theMME 20 determines that a priority of the second network connection request is a non-low priority, theMME 20 sends a timing stop message to the user equipment, and controls theuser equipment 10 to establish the connection having a non-low priority to the network. A process of establishing a network connection having a non-low priority is used below as an example for description. -
FIG. 5 is a schematic diagram of a process in which theMME 20 controls theuser equipment 10 to establish a connection having a non-low priority to the network according to the first embodiment of the present invention. - When the network connection request is an attach request, and a priority of the attach request is a non-low priority, the
MME 20 controls theuser equipment 10 to establish a network connection having a non-low priority. Specifically,step 231 is performed. - When the
user equipment 10 has already established a bearer having a low priority to a network, and when theuser equipment 10 needs to send service data having a non-low priority, the bearer having a low priority cannot implement transmission of the service data having a non-low priority. Then theuser equipment 10 establishes a network connection having a non-low priority by sending a PDN connection request having a non-low priority. Specifically,step 233 is performed, where the attach request or the PDN connection request carries an identifier, and/or priority information, and/or a group identifier of theuser equipment 10. - Step 231: The
MME 20 sends a location update request to an HSS according to the network connection request. - Step 232: The HSS, in response to the location update request, sends subscription data of the
user equipment 10 to theMME 20, where the subscription data includes subscription information, such as a subscription group identifier of theuser equipment 10. - Step 233: If the
MME 20 determines, according to the subscription information, that theuser equipment 10 belongs to a preset user equipment group, theMME 20 establishes a public bearer having a non-low priority or a public PDN connection having a non-low priority for a user equipment in the preset user equipment group according to a trigger request of theuser equipment 10, so that other user equipments in the preset user equipment group may use the public bearer or public PDN connection to perform data transmission. - Specifically, step 2331: The
MME 20 sends a create session request message to an S-GW, where the request message carries public bearer information, such as the group identifier and a public bearer identifier. - Step 2332: The S-GW sends the create session request message to a P-GW, where the request message carries the public bearer information, such as the group identifier and the public bearer identifier.
- It can be understood that, the S-GW determines whether a public bearer has been established for the user equipment group, and if the public bearer has been established,
step 2334 is performed; otherwise, a create session request is sent to the P-GW. - Step 2333: The P-GW generates an accounting ID for the public bearer, and sends a create session response message to the S-GW, where the response message carries a public bearer resource, such as a public bearer identifier.
- Step 2334: The S-GW sends the create session response message to the
MME 20, where the response message carries a public bearer resource, such as the public bearer identifier. - Step 2335: The
MME 20 sends an attach accept message or a PDN connection accept message to a base station eNodeB, where the accept message carries public bearer information, such as the public bearer identifier. - Step 2336: The base station eNodeB and the
user equipment 10 complete an RRC (Radio Resource Control, radio resource control protocol) connection reallocation process, and establish a radio access bearer. - Step 2337: The base station eNodeB sends an attach complete message or a PDN connection complete message to the
MME 20, where the message carries a public bearer resource, such as the public bearer identifier, an eNodeB address, and an identifier TEID. - Step 2338: The
MME 20 sends a modify bearer request message to the S-GW, where the message carries a public bearer resource, such as the public bearer identifier, the eNodeB address, and a channel port identifier TEID. - Step 2339: The S-GW creates a mapping between the public bearer and the access bearer.
- For example, a mapping among an identifier of the
user equipment 10 or an IP address of theuser equipment 10, a group identifier, a public bearer identifier, an eNodeB TEID, a S-GW TEID and so on is established. - Step 2340: The S-GW sends a modify bearer response message to the
MME 20. - Step 2341: The
user equipment 10 of the preset user equipment group sends or receives data by means of the public bearer. - For example, when the
user equipment 10 of the preset user equipment group sends the data, an uplink data packet is sent to the S-GW by means of the access bearer, then the S-GW finds a corresponding S-GW TEID or public bearer identifier according to the identifier or IP address or group identifier of theuser equipment 10, forwards the data to a corresponding public bearer port, and sends the data to the P-GW by means of the public bearer port. The public bearer and a default bearer having a non-low priority may transmit service data having a non-low priority, and may also transmit service data having a low priority; eachuser equipment 10 belonging to the preset user equipment group may transmit the service data by means of the public bearer. - In this embodiment, the
MME 20 controls the preset user equipment group to establish a public bearer or a public PDN connection, so that theuser equipment 10 belonging to the preset user equipment group may transmit service data having a low priority or a non-low priority by means of the public bearer, or transmit service data having a non-low priority by means of the public PDN connection, which avoids repeatedly establishing a respective bearer or PDN connection for eachuser equipment 10 belonging to the preset user equipment group, thereby saving network resources. - Optionally, in
step 233, if theMME 20 determines, according to the subscription information of theuser equipment 10, that theuser equipment 10 does not belong to the preset user equipment group, theMME 20 controls thesingle user equipment 10 to establish a bearer having a non-low priority or a PDN connection having a non-low priority. -
FIG. 6 is a schematic diagram of controlling thesingle user equipment 10 to establish a connection having a non-low priority to a network by theMME 20 according to the first embodiment of the present invention. A process of establishing a network connection having a non-low priority is described by using an example in which the network connection having a non-low priority is established after a network connection having a low priority is established between theuser equipment 10 and the network. - Step 261: The
user equipment 10 is attached to the network to establish a bearer having a low priority. - Step 262: The
user equipment 10 sends a service data transmission request having a low priority. - Step 263: The
MME 20 determines that a priority of the transmission request is a low priority, and if the network is overloaded, theMME 20 refuses to receive the request of theuser equipment 10, and sends, to theuser equipment 10, a rejecting message carrying a back-off time; if the network is not overloaded,step 267 is performed. - Step 264: The
user equipment 10 starts timing of a back-off timer according to the back-off time in the rejecting message, and does not send a connection request having a low priority within a timing time. - Step 265: The
MME 20 receives a PDN connection request having a non-low priority of theuser equipment 10, and sends a timing stop command to theuser equipment 10. - Step 266: The
user equipment 10 stops timing of the back-off timer according to the timing stop command, and allows theuser equipment 10 to send a network connection request having a low priority. - Step 267: The
MME 20 controls establishment of the PDN connection having a non-low priority between theuser equipment 10 and the network according to the PDN connection request having a non-low priority. - It can be understood that, the
single user equipment 10 may also send an attach request having a non-low priority to theMME 20, and if theMME 20 determines that a priority of the attach request is a non-low priority, theMME 20 accepts the attach request, and establishes a network connection having a non-low priority for theuser equipment 10. - It can be understood that, the process in which the
single user equipment 10 establishes the network connection having a non-low priority or a low priority to the network is similar to the foregoing process in which the preset user equipment group establishes a public bearer or a public PDN connection to the network, which is not described herein again. - It can be understood that, if the
user equipment 10 supports multiple PDN connections, the priority information may further include different APNs (Access Point Name, access point name). TheMME 20 identifies connection requests having different priorities according to different APN values. For example, APN1 indicates a connection request having a low priority, and APN2 indicates a connection request having a non-low priority. TheMME 20 may determine a priority of a connection request according to the APN value. - It can be understood that, for the
user equipment 10 supporting a single PDN connection, an existing PDN connection needs to be deleted and a new PDN connection needs to be established before a new PDN connection request is initiated. A specific process in which the PDN connection is deleted is a technology known by a person skilled in the art, does not affect clear descriptions of the main technical solution in the embodiment of the present invention, and is not described herein again. - It can be understood that, the
MME 20 may also predefine a limit value for theuser equipment 10 that may establish a network connection having a non-low priority. When theMME 20 determines thatuser equipment 10 having established the network connections having a non-low priority exceeds the limit value, whether the network is overloaded or not, theMME 20 rejects the connection request having a non-low priority sent by theuser equipment 10. - It can be further understood that, for the
user equipment 10 belonging to the preset user equipment group, theMME 20 may further set a limit value for the number of user equipments belonging to the preset user equipment group and establishing connections having a non-low priority to the network. When theMME 20 determines that the number of the user equipments establishing connections having a non-low priority to the network and in the preset user equipment group exceeds the limit value, theMME 20 rejects the connection request having a non-low priority sent by theuser equipment 10. TheMME 20 protects the network by controlling the number of the user equipments establishing network connections, which avoids network paralysis caused by occupancy of network resources by multiple user equipments unlimitedly establishing network connections having a non-low priority. - It can be further understood that, an order in which the
MME 20 determines the priority of the network connection request and determines the network overload state is not limited. - In this embodiment of the present invention, the mobility
management entity MME 20 may selectively control the connection between theuser equipment 10 and the network by determining the priority of the network connection request and the network overload state. - According to the descriptions of the foregoing embodiment,
FIG. 7 is a schematic structural diagram of a mobilitymanagement entity MME 30 that controls a connection between a user equipment and a network according to a second embodiment of the present invention. - Based on the first embodiment of the present invention, the mobility
management entity MME 30 may be applied to a 3GPP evolved packet system EPS (Evolved Packet System), and the evolved packet system EPS includes: an Evolved Universal Terrestrial Radio Access Network (E-UTRAN, Evolved Universal Terrestrial Radio Access Network), a mobility management entity (Mobility Management Entity, MME for short), a serving gateway (Serving Gateway, S-GW for short), a packet data network gateway (Packet Data Network Gateway, P-GW for short), a home subscriber server (Home Subscriber Server, HSS for short), a 3GPP authentication, authorization and accounting (Authentication Authorization and Accounting, AAA for short) server, a policy and charging rules function (Policy and Charging Rules Function, PCRF for short) and other support nodes. TheMME 30 is responsible for functions, such as mobility management, processing of non-access-stratum (Non-Access-Stratum, NAS for short) signaling, control plane related operations such as management of a user mobility context, reachability management for a mobile terminal in an idle state selected by the P-GW and the S-GW, and selecting of a tracking area list. - The mobility
management entity MME 30 includes atransceiver 31 and aprocessor 32. Thetransceiver 31 receives a network connection request sent by auser equipment 10; theprocessor 32 determines a priority of the network connection request and a network overload state, and further controls a connection between theuser equipment 10 and a network according to the priority of the network connection request and the network overload state. - In this embodiment of the present invention, the mobility
management entity MME 30 may selectively control the connection between theuser equipment 10 and the network by determining the priority of the network connection request and the network overload state. - The
transceiver 31 is configured to receive and send information in an information receiving and sending process or a call process, and thetransceiver 31 may communicate with other devices by using a wireless communications system and the network. According to the embodiment of the present invention, thetransceiver 31 receives the network connection request sent by theuser equipment 10, and sends, according to the priority of the network connection request and the network overload state, information about controlling establishment of the connection between theuser equipment 10 and the network. - That the
processor 32 determines a priority of the network connection request includes: theprocessor 32 determines whether priority information is carried in the network connection request; and if priority information is carried, the priority of the network connection request is determined according to the priority information; if the priority information is not carried, it is determined that the priority of the network connection request is a non-low priority. - The priority information is preconfigured in the
user equipment 10, and a configuration process of the priority is based on the first embodiment and similar to the process of configuring the priority information described inFIG. 3 . - Optionally or further, that the
processor 32 determines the network overload state includes: theprocessor 32 may determine the network overload state according to an idle state of network resources. - For example, if the
processor 32 determines that an idle network resource exists, theprocessor 32 determines that the network is overloaded; if theprocessor 32 determines that no idle network resource exists, theprocessor 32 determines that the network is not overloaded. - Optionally, the
processor 32 may determine the network overload state according to a network overload control command. - For example, if the
processor 32 determines that the network overload control command is received, theprocessor 32 determines that the network is overloaded; if theprocessor 32 determines that no network overload control command is received, theprocessor 32 determines that the network is not overloaded. - It can be understood that, the network overload control command can be triggered when a device operator or manufacturer maintains a device or be triggered when a device is faulty.
- Further, that the
processor 32 controls a connection between theuser equipment 10 and a network according to the priority of the network connection request and the network overload state includes: - the
processor 32 rejects the network connection request of theuser equipment 10 according to that the priority of the network connection request is a low priority and the network is overloaded, and sends, to theuser equipment 10, a rejecting message carrying a back-off time; and theprocessor 32 does not receive, in the back-off time, the network connection request having a low priority sent by theuser equipment 10. - Optionally, if the
processor 32 determines that the priority of the network connection request is a low priority or a non-low priority, and determines that the network is not overloaded, theMME 20 controls theuser equipment 10 to establish a network connection having a low priority or a non-low priority. - Optionally, after the
processor 32 determines that the priority of the network connection request is a low priority, determines that the network is overloaded, rejects the network connection request having a low priority, and sends, to theuser equipment 10, the rejecting message carrying the back-off time, theprocessor 32, in the back-off time, receives a second network connection request sent by theuser equipment 10, sends a timing stop message to theuser equipment 10 if it is determined that a priority of the second network connection request is a non-low priority, and controls establishment of a connection having a non-low priority between theuser equipment 10 and the network. - After the
processor 32 determines that theuser equipment 10 meets a condition of establishing the connection having a non-low priority to the network, that the controlling establishment of a connection having a non-low priority between theuser equipment 10 and the network includes: - if the
processor 32 determines, according to subscription information of theuser equipment 10, that theuser equipment 10 belongs to a preset user equipment group, theprocessor 32 controls theuser equipment 10 to establish a public bearer having a non-low priority or a public PDN connection having a non-low priority according to a connection request having a non-low priority of theuser equipment 10. - Optionally, if the
processor 32 determines, according to subscription information of theuser equipment 10, that theuser equipment 10 does not belong to a preset user equipment group, theprocessor 32 controls theuser equipment 10 to establish a single bearer having a non-low priority or a single PDN connection having a non-low priority to the network. In this embodiment, the process in which theprocessor 32 controls theuser equipment 10 to establish a network connection is similar to that in the first embodiment, and is not described herein again. - It can be understood that, if the
user equipment 10 supports multiple PDN connections, the priority information may further include different APNs (Access Point Name, access point name). Theprocessor 32 identifies connection requests having different priorities according to different APN values. For example, APN1 indicates a connection request having a low priority, and APN2 indicates a connection request having a non-low priority. Theprocessor 32 may determine a priority of a connection request according to the APN value. - It can be understood that, for the
user equipment 10 supporting a single PDN connection, an existing PDN connection needs to be deleted and a new PDN connection needs to be re-established before a new PDN connection request is initiated. A specific process in which the PDN connection is deleted is a technology known by a person skilled in the art, does not affect clear descriptions of the main technical solution in the embodiment of the present invention, and is not described herein again. - It can be understood that, the
processor 32 may also predefine a limit value for theuser equipment 10 that may establish a network connection having a non-low priority. When theprocessor 32 determines that theuser equipment 10 establishing the network connection having a non-low priority exceeds the limit value, whether the network is overloaded or not, theprocessor 32 rejects the connection request having a non-low priority sent by theuser equipment 10. - It can be further understood that, for the
user equipment 10 belonging to the preset user equipment group, theprocessor 32 may further set a limit value for the number of user equipments belonging to the preset user equipment group and establishing connections having a non-low priority to the network. When theprocessor 32 determines that the number of the user equipments establishing connections having a non-low priority to the network and in the preset user equipment group exceeds the limit value, theprocessor 32 rejects the connection request having a non-low priority sent by theuser equipment 10. Theprocessor 32 protects the network by controlling the number of the user equipments establishing network connections, which avoids network paralysis caused by occupancy of network resources by unlimitedly establishing the network connections having a non-low priority by multiple user equipments. - It can be further understood that, an order in which the
processor 32 determines the priority of the network connection request and determines the network overload state is not limited. - In this embodiment, the
MME 30 may further include amemory 34, and thememory 34 may be configured to store an uplink control instruction or data information sent by an M2M, and store uplink and downlink control signaling and data information between theMME 30 and the S-GW or between theMME 30 and the P-GW. Thememory 34 may be integrated with the HSS. - According to the embodiment of the present invention, the mobility
management entity MME 40 may selectively control the connection between theuser equipment 10 and the network by determining the priority of the network connection request and the network overload state. -
FIG. 8 is a schematic diagram of a mobility management entity that controls a connection between a user equipment and a network according to a third embodiment of the present invention. - A technical solution of this embodiment is further described based on the technical solution described in the first embodiment of the present invention. A
mobility management entity 40 includes atransmission module 41, a determiningmodule 43, and acontrol module 45. - The
transmission module 41 receives a network connection request sent by auser equipment 10. - The determining
module 43 determines a priority of the network connection request and a network overload state. - The
control module 45 controls a connection between theuser equipment 10 and the network according to the priority of the network connection request and the network overload state. - According to the embodiment of the present invention, the mobility
management entity MME 40 may selectively control the connection between theuser equipment 10 and the network by determining the priority of the network connection request and the network overload state. - The
transmission module 41 receives a network connection request which carries priority information sent by theuser equipment 10, where the priority information indicates the priority of the network connection request; or receives a network connection request which does not carry priority information and is sent by theuser equipment 10. - The priority information may indicate that the priority of the network connection request is a low priority or a non-low priority. In other embodiments, the non-low priority may further include multiple levels, such as a medium priority and a high priority. The priority information is preconfigured in the
user equipment 10, and a configuration process of the priority is based on the first embodiment and similar to the process of configuring the priority information described inFIG. 3 . - That the determining
module 43 determines a priority of the network connection request includes: - the determining
module 43 determines whether the network connection request carries the priority information; and if priority information is carried, the priority of the network connection request is determined according to the priority information; if the priority information is not carried, it is determined that the priority of the network connection request is a non-low priority. - Optionally or further, that the determining
module 43 determines the network overload state includes: - the determining
module 43 may determine the network overload state according to an idle state of network resources. - For example, if the determining
module 43 determines that an idle network resource exists, the determiningmodule 43 determines that the network is overloaded; if the determiningmodule 43 determines that no idle network resource exists, the determiningmodule 43 determines that the network is not overloaded. - Optionally, the determining
module 43 may determine the network overload state according to a network overload control command. - For example, if the determining
module 43 determines that the network overload control command is received, the determiningmodule 43 determines that the network is overloaded; if the determiningmodule 43 determines that no network overload control command is received, the determiningmodule 43 determines that the network is not overloaded. - It can be understood that, the network overload control command can be triggered when a device operator or manufacturer maintains a device or be triggered when a device is faulty.
- Further, that the
control module 45 controls a connection between theuser equipment 10 and the network according to the priority of the network connection request and the network overload state includes: - the
control module 45 rejects the network connection request of theuser equipment 10 according to that the priority of the network connection request is a low priority and the network is overloaded, and sends, to theuser equipment 10, a rejecting message carrying a back-off time; and thecontrol module 45 does not receive, in the back-off time, the network connection request having a low priority sent by theuser equipment 10. - Optionally, if the
control module 45 determines that the priority of the network connection request is a low priority or a non-low priority, and determines that the network is not overloaded, thecontrol module 45 controls theuser equipment 10 to establish a network connection with a low priority or a non-low priority. - Optionally, after the
control module 45 determines that the priority of the network connection request is a low priority, determines that the network is overloaded, rejects the network connection request having a low priority and sends, to theuser equipment 10, the rejecting message carrying the back-off time, thecontrol module 45, in the back-off time, receives a second network connection request sent by theuser equipment 10; sends a timing stop message to theuser equipment 10 if it is determined that a priority of the second network connection request is a non-low priority, thecontrol module 45, and controls establishment of a connection having a non-low priority between theuser equipment 10 and the network. - After the
control module 45 determines that theuser equipment 10 meets a condition of establishing the connection having a non-low priority to the network, that the controlling establishment of a connection having a non-low priority between theuser equipment 10 and the network includes: - if the
control module 45 determines, according to subscription information of theuser equipment 10, that theuser equipment 10 belongs to a preset user equipment group, thecontrol module 45 controls theuser equipment 10 to establish a public bearer having a non-low priority or a public PDN connection having a non-low priority according to a connection request having a non-low priority of theuser equipment 10. - Optionally, if the
control module 45 determines, according to subscription information of theuser equipment 10, that theuser equipment 10 does not belong to a preset user equipment group, thecontrol module 45 controls theuser equipment 10 to establish a single bearer having a non-low priority or a single PDN connection having a non-low priority to the network. In this embodiment, the process in which thecontrol module 45 controls theuser equipment 10 to establish a network connection is similar to that in the first embodiment, and is not described herein again. - It can be understood that, if the
user equipment 10 supports multiple PDN connections, the priority information may further include different APNs (Access Point Name, access point name). Thecontrol module 45 identifies connection requests having different priorities according to different APN values. For example, APN1 indicates a connection request having a low priority, and APN2 indicates a connection request having a non-low priority. Thecontrol module 45 may determine a priority of a connection request according to the APN value. - It can be understood that, for the
user equipment 10 supporting the single PDN connection, an existing PDN connection needs to be deleted and a new PDN connection needs to be established before a new PDN connection request is initiated. A specific process in which the PDN connection is deleted is a technology known by a person skilled in the art, does not affect clear descriptions of the main technical solution in the embodiment of the present invention, and is not described herein again. - It can be understood that, the
control module 45 may also predefine a limit value for theuser equipment 10 that may establish a network connection having a non-low priority. When thecontrol module 45 determines that theuser equipment 10 establishing the network connection having a non-low priority exceeds the limit value, whether the network is overloaded or not, thecontrol module 45 rejects the connection request having a non-low priority sent by theuser equipment 10. - It can be further understood that, for the
user equipment 10 belonging to the preset user equipment group, thecontrol module 45 may further set a limit value for the number of user equipments belonging to the preset user equipment group and establishing connections having a non-low priority to the network. When thecontrol module 45 determines that the number of the user equipments establishing connections having a non-low priority to the network and in the preset user equipment group exceeds the limit value, thecontrol module 45 rejects the connection request having a non-low priority sent by theuser equipment 10. Thecontrol module 45 protects the network by controlling the number of the user equipments establishing network connections, which avoids network paralysis caused by occupancy of network resources by unlimitedly establishing the network connections having a non-low priority by multiple user equipments. - It can be further understood that, an order in which the
control module 45 determines the priority of the network connection request and determines the network overload state is not limited. - According to the embodiment of the present invention, the mobility
management entity MME 40 may selectively control the connection between theuser equipment 10 and the network by determining the priority of the network connection request and the network overload state. -
FIG. 9 is a structural diagram of auser equipment 50 that controls a connection to a network according to a fourth embodiment of the present invention. - The user equipment 50in the embodiment of the present invention may be an M2M device, for example, a fixed or mobile machine-to-machine communications device such as a temperature tester, or a water/electricity meter.
- The
user equipment 50 includes atransmission module 52, atiming module 53, and acontrol module 54, where: - the
transmission module 52 sends a network connection request to a mobility management entity 60; - the
transmission module 52 receives a rejecting message which carries a back-off time and is sent by the mobility management entity 60; - the
timing module 53 starts a timer according to the back-off time in the rejecting message; and - the
control module 54 , in the back-off time, forbids theuser equipment 50 to send a network connection request having a low priority, and allows theuser equipment 50 to send a network connection request having a non-low priority. - The
user equipment 50 in the embodiment of the present invention, according to the rejecting message sent by the mobility management entity 60, forbids theuser equipment 50 to send the network connection request having a low priority, and allows theuser equipment 50 to send the network connection request having a non-low priority, which prevents theuser equipment 50 from continuously sending network connection requests having a low priority to a network, and avoids blocking the network. - That the
transmission module 52 sends a network connection request to a mobility management entity 60 includes: thetransmission module 52 may send, to the mobility management entity 60, a network connection request which carries priority information, or send, to the mobility management entity 60, a network connection request which does not carry priority information. - It can be understood that, if the network connection request does not carry the priority information, the mobility management entity 60 may determine that the default priority of the network connection request is a non-low priority.
- It can be understood that, when the
user equipment 50 acquires service data having a non-low priority, thecontrol module 54, in the back-off time, controls theuser equipment 50 to send a network connection request having a non-low priority to the mobility management entity 60, and stops timing of the timer according to timing stop signaling sent for the network connection request having a non-low priority by the mobility management entity 60. - The
user equipment 50 in the embodiment of the present invention may further include adetection module 55, a determiningmodule 56, and a configuration module 57, where thedetection module 55 is configured to detect and acquire service data, such as temperature data and water/electricity data. - The determining
module 56 determines a priority of the service data acquired by the detection module. - The configuration module 57 configures priority information corresponding to the priority of the service data.
- For specific solutions executed by the determining
module 56 and the configuration module 57, refer to the descriptions in the first embodiment, which are not described herein again. Theuser equipment 50 in the embodiment of the present invention, according to the rejecting message sent by the mobility management entity 60, forbids theuser equipment 50 to send network connection request having a low priority, and allows theuser equipment 50 to send network connection request having a non-low priority, which prevents theuser equipment 50 from continuously sending network connection requests having a low priority to a network, and avoids blocking the network. -
FIG. 10 is a flowchart of a method for controlling a connection between a user equipment and a network according to a fifth embodiment of the present invention. - The method for controlling the connection between the
user equipment 50 and the network includes: - Step 101: The
user equipment 50 sends a network connection request to a mobility management entity 60. - Step 102: The
user equipment 50 receives a rejecting message which carries a back-off time and is sent by the mobility management entity 60. - Step 103: The
user equipment 50 starts a timer according to the back-off time in the rejecting message. - Step 104: The
user equipment 50, in the back-off time, forbids the user equipment to send a network connection request having a low priority, and allows the user equipment to send a network connection request having a non-low priority to the mobility management entity 60. - According to the method for controlling the connection between the
user equipment 50 and the network in the embodiment of the present invention, theuser equipment 50 is, according to the rejecting message sent by the mobility management entity 60, forbidden to send the network connection request having a low priority, and allowed to send the network connection request having a non-low priority, which prevents theuser equipment 50 from continuously sending network connection requests having a low priority to a network, and avoids blocking the network. - In
step 101, theuser equipment 50 may send, to the mobility management entity 60, a network connection request which carries priority information, or send, to the mobility management entity 60, a network connection request which does not carry priority information. - In
step 104, that theuser equipment 50 is allowed to send the network connection request having a non-low priority to the mobility management entity 60 in the back-off time includes: - in the back-off time, when the
user equipment 50 acquires the service data having a non-low priority, theuser equipment 50 sends the network connection request having a non-low priority to the mobility management entity 60. - Further, after the
user equipment 50 controls, in the back-off time, theuser equipment 50 to send the network connection request having a non-low priority to the mobility management entity 60, the method further includes: theuser equipment 50 stops timing of the timer according to timing stop signaling sent for the network connection request having a non-low priority by the mobility management entity 60. - According to the method for controlling the connection between the user equipment and the network in this embodiment, the
user equipment 50 is, according to the rejecting message sent by the mobility management entity 60, forbidden to send the network connection request having a low priority, and allowed to send the network connection request having a non-low priority, which may selectively control the connection between the user equipment and the network. - It should be understood by a person of ordinary skill in the art that exemplary modules and algorithm steps described with reference to the disclosed embodiments of this specification may be implemented by means of electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should be considered that the implementation does not go beyond the scope of the present invention.
- It should be clearly understood by a person skilled in the art that for ease and brevity of description, reference may be made to corresponding processes in the foregoing method embodiments for the specific working processes of the electronic devices, devices, and modules described above, which are not described herein again.
- In several embodiments provided in this application, it should be understood that, the disclosed system, device, and method may be implemented in other manners. The electronic device embodiments described above are merely exemplary, for example, the division of the modules is merely division according to logical functions, and another division manner may be available when actual implementation is performed.
- In addition, various function modules in the embodiments of the present invention may be integrated in one processing device, or modules may exist physically independently, or two or more than two modules may be integrated in one device.
- When the function is implemented in a software function device form and is sold or used as an independent product, the function may be stored in a computer readable storage medium. Based on such an understanding, the technical solutions of the present invention essentially, or the part contributing to the prior art, or a part of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or a part of the steps of the methods described in the embodiments of the present invention. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.
- The foregoing descriptions are merely specific implementation manners of the present invention, but are not intended to limit the protection scope of the present invention. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in the present invention shall fall within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (18)
- A method for controlling a connection between a user equipment and a network, comprising:receiving, by a mobility management entity, a network connection request sent by the user equipment;determining, by the mobility management entity, a priority of the network connection request and a network overload state; andcontrolling, by the mobility management entity, the connection between the user equipment and the network according to the priority of the network connection request and the network overload state.
- The method according to claim 1, wherein the controlling, by the mobility management entity, a connection between the user equipment and a network according to the priority of the network connection request and the network overload state comprises:rejecting, by the mobility management entity according to that the priority of the connection request is a low priority and the network is overloaded, the network connection request having the low priority
- The method according to claim 2, wherein after the sending, by the mobility management entity to the user equipment, a rejecting message carrying a back-off time, the method further comprises:receiving, by the mobility management entity in the back-off time, a second network connection request sent by the user equipment; andwhen the mobility management entity determines that a priority of the second network connection request is a non-low priority, sending a timing stop instruction to the user equipment, and controlling establishment of a connection having a non-low priority between the user equipment and the network.
- The method according to claim 1, wherein the controlling, by the mobility management entity, a connection between the user equipment and a network according to the priority of the network connection request and the network overload state comprises:when the mobility management entity determines that the priority of the connection request is a low priority or a non-low priority, and determines that the network is not overloaded, controlling establishment of a connection having a corresponding priority between the user equipment and the network.
- The method according to claim 3 or 4, wherein the controlling, by the mobility management entity, establishment of a connection having a non-low priority between the user equipment and the network comprises:when the mobility management entity determines, according to subscription information of the user equipment, that the user equipment does not belong to a preset user equipment group, controlling establishment of a bearer having a non-low priority or a PDN connection having a non-low priority between the user equipment and the network.
- The method according to claim 3 or 4, wherein the controlling, by the mobility management entity, a connection between the user equipment and the network comprises:when the mobility management entity determines, according to subscription information of the user equipment, that the user equipment belongs to a preset user equipment group, controlling establishment of a public bearer having a non-low priority or a public PDN connection having a non-low priority between the user equipment and the network.
- The method according to any one of claims 1 to 6, wherein the controlling a connection between the user equipment and a network according to the priority of the network connection request and the network overload state comprises:when the mobility management entity determines that the priority of the network connection request is a non-low priority, and determines that the number of user equipments having established network connections having a non-low priority exceeds a limit value, rejecting the connection request having a non-low priority sent by the user equipment.
- The method according to any one of claims 1 to 7, wherein the determining, by the mobility management entity, a priority of the network connection request comprises:when the mobility management entity determines that the network connection request carries priority information, determining the priority of the network connection request according to the priority information.
- The method according to claim 8, wherein the determining the priority of the network connection request according to the priority information comprises:determining, by the mobility management entity, the priority of the network connection request according to a correspondence between an access point name APN and a priority in the priority information.
- The method according to any one of claims 1 to 7, wherein the determining, by the mobility management entity, a priority of the network connection request comprises:when the mobility management entity determines that the network connection request does not carry priority information, determining that the priority of the network connection request is a non-low priority.
- The method according to any one of claims 1 to 10, wherein the determining, by the mobility management entity, a network overload state comprises:determining, by the mobility management entity, the network overload state according to an idle state of network resources; and/or determining, by the mobility management entity, the network overload state according to a network overload control command.
- A mobility management entity, comprising a transmission module, a determining module, and a control module, wherein:the transmission module receives a network connection request sent by a user equipment;the determining module determines a priority of the network connection request and a network overload state; andthe control module controls a connection between the user equipment and a network according to the priority of the network connection request and the network overload state.
- The mobility management entity according to claim 12, wherein that the control module controls a connection between the user equipment and a network according to the priority of the network connection request and the network overload state comprises:the control module rejects a network connection request having a low priority according to that the priority of the connection request is the low priority and the network is overloaded, and sends, to the user equipment, a rejecting message carrying a back-off time.
- The mobility management entity according to claim 13, wherein after the control module sends, to the user equipment, a rejecting message carrying the back-off time, the method further comprises:the control module receives, in the back-off time, a second network connection request sent by the user equipment; andwhen the control module determines that a priority of the second network connection request is a non-low priority, the control module sends a timing stop instruction to the user equipment, and controls establishment of a connection having a non-low priority between the user equipment and the network.
- A user equipment, comprising a transmission module, a timing module, and a control module, wherein:the transmission module sends a network connection request to a mobility management entity;the transmission module receives a rejecting message which carries a back-off time and is sent by the mobility management entity;the timing module starts a timer according to the back-off time in the rejecting message; andthe control module , in the back-off time, forbids the user equipment to send a network connection request having a low priority, and allows the user equipment to send a network connection request having a non-low priority to the mobility management entity.
- The user equipment according to claim 15, wherein the network connection request carries priority information, or does not carry priority information.
- The user equipment according to claim 15 or 16, wherein that the control module allows, in the back-off time, the network connection request having a non-low priority to be sent to the mobility management entity comprises: the control module controls, in the back-off time, the user equipment to send the network connection request having a non-low priority to the mobility management entity when the user equipment acquires service data having a non-low priority.
- The user equipment according to claim 17, wherein after the control module controls the user equipment to send the network connection request having a non-low priority to the mobility management entity, further comprising: the control module stops timing of the timer according to timing stop signaling sent for the network connection request having a non-low priority by the mobility management entity.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210370562.6A CN103716761B (en) | 2012-09-29 | 2012-09-29 | Control the method and mobile management device of user equipment and network connection |
PCT/CN2013/072009 WO2014048085A1 (en) | 2012-09-29 | 2013-02-28 | Control method for the connection between user equipment and network and mobile management equipment |
Publications (3)
Publication Number | Publication Date |
---|---|
EP2811767A1 true EP2811767A1 (en) | 2014-12-10 |
EP2811767A4 EP2811767A4 (en) | 2015-08-05 |
EP2811767B1 EP2811767B1 (en) | 2020-11-11 |
Family
ID=50386929
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13841822.3A Active EP2811767B1 (en) | 2012-09-29 | 2013-02-28 | Control method for the connection between user equipment and network and mobile management equipment |
Country Status (4)
Country | Link |
---|---|
US (3) | US9668286B2 (en) |
EP (1) | EP2811767B1 (en) |
CN (2) | CN108064067A (en) |
WO (1) | WO2014048085A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016003330A1 (en) * | 2014-06-30 | 2016-01-07 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatuses for determining priority of a wireless terminal |
GB2582651A (en) * | 2019-03-29 | 2020-09-30 | Sony Corp | A device, computer program and method |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108064067A (en) * | 2012-09-29 | 2018-05-22 | 华为终端有限公司 | Control the method and mobile management device of user equipment and network connection |
CN104468649B (en) * | 2013-09-16 | 2018-06-05 | 北大方正集团有限公司 | Server, terminal, data delivery system and data push method |
EP3205123B1 (en) * | 2014-10-07 | 2020-04-22 | Telefonaktiebolaget LM Ericsson (publ) | Paging procedure for a wireless device, a radio access node, methods performed therein, a computer program, and a computer-readable storage medium |
EP3094119B1 (en) * | 2015-05-13 | 2019-08-28 | Telia Company AB | Session management |
CN106658601B (en) * | 2015-10-28 | 2021-05-11 | 中兴通讯股份有限公司 | Data transmission processing method and device |
US10142923B2 (en) * | 2016-02-26 | 2018-11-27 | Microsoft Technology Licensing, Llc | Using a single packet data network for data transfers to manage network resources |
US10098066B2 (en) * | 2016-06-27 | 2018-10-09 | Microsoft Technology Licensing, Llc | Auxiliary back-off to avoid battery and network resource depletion in variable network conditions |
CN106332311A (en) * | 2016-08-22 | 2017-01-11 | 广东工业大学 | LTE-based data transmission method for Internet of Things |
US10271376B2 (en) * | 2016-09-29 | 2019-04-23 | Intel IP Corporation | Optimized transmission for priority data on a radio access technology network |
CN112333113A (en) * | 2020-05-18 | 2021-02-05 | 中兴通讯股份有限公司 | Information processing method, terminal and computer readable storage medium |
CN113949674A (en) * | 2020-06-29 | 2022-01-18 | 成都鼎桥通信技术有限公司 | Data transmission method, system, network equipment, media equipment and receiving equipment |
WO2022049082A1 (en) * | 2020-09-04 | 2022-03-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Technique for barring a radio device from radio access in a radio access network |
CN116095019B (en) * | 2022-08-19 | 2024-03-26 | 荣耀终端有限公司 | Route processing method, device, equipment and storage medium |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101292469A (en) * | 2005-08-19 | 2008-10-22 | 意大利电信股份公司 | Management of anonymous communications between customers based on short-distance wireless connection identifier |
CN101610494B (en) * | 2008-06-16 | 2013-04-24 | 华为技术有限公司 | Method, system and equipment for realizing overload control or differentiated services |
US8565242B2 (en) | 2008-11-04 | 2013-10-22 | Blackberry Limited | Transport protocol performance using network bit rate information |
KR101331866B1 (en) | 2009-01-15 | 2013-11-22 | 블랙베리 리미티드 | System and method for determining establishment causes |
CN102223729B (en) * | 2010-04-16 | 2016-06-29 | 中兴通讯股份有限公司 | Control machine type communication device and access the method and system of network |
CN101969635A (en) * | 2010-04-30 | 2011-02-09 | 中兴通讯股份有限公司 | Access control method and system for machine communication |
US8705352B2 (en) | 2010-09-10 | 2014-04-22 | Industrial Technology Research Institute | Prioritized random access method |
US8593956B2 (en) * | 2010-12-21 | 2013-11-26 | Htc Corporation | Methods for congestion control for machine type communication (MTC) devices or low priority devices, and apparatuses using the same |
CN102111847B (en) | 2011-01-10 | 2013-07-24 | 大唐移动通信设备有限公司 | Access control method and device |
KR20120094369A (en) * | 2011-02-16 | 2012-08-24 | 주식회사 팬택 | Method and apparatus for rrc connection establishment in mtc |
TW201251494A (en) * | 2011-02-24 | 2012-12-16 | Interdigital Patent Holdings | Handling of low priority devices |
CN102256373A (en) * | 2011-07-21 | 2011-11-23 | 中兴通讯股份有限公司 | Call accessing method and system |
CN102333343A (en) * | 2011-11-02 | 2012-01-25 | 电信科学技术研究院 | Congestion information notification method and equipment |
CN102547912B (en) * | 2012-01-17 | 2015-08-05 | 电信科学技术研究院 | A kind of connection control method and device |
CN108064067A (en) * | 2012-09-29 | 2018-05-22 | 华为终端有限公司 | Control the method and mobile management device of user equipment and network connection |
-
2012
- 2012-09-29 CN CN201711437277.0A patent/CN108064067A/en active Pending
- 2012-09-29 CN CN201210370562.6A patent/CN103716761B/en active Active
-
2013
- 2013-02-28 EP EP13841822.3A patent/EP2811767B1/en active Active
- 2013-02-28 WO PCT/CN2013/072009 patent/WO2014048085A1/en active Application Filing
-
2014
- 2014-12-30 US US14/585,501 patent/US9668286B2/en active Active
-
2017
- 2017-04-24 US US15/495,578 patent/US10412771B2/en active Active
-
2019
- 2019-07-29 US US16/524,812 patent/US11363647B2/en active Active
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016003330A1 (en) * | 2014-06-30 | 2016-01-07 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatuses for determining priority of a wireless terminal |
GB2582651A (en) * | 2019-03-29 | 2020-09-30 | Sony Corp | A device, computer program and method |
Also Published As
Publication number | Publication date |
---|---|
US20190357279A1 (en) | 2019-11-21 |
EP2811767A4 (en) | 2015-08-05 |
US10412771B2 (en) | 2019-09-10 |
US20150117192A1 (en) | 2015-04-30 |
US9668286B2 (en) | 2017-05-30 |
WO2014048085A1 (en) | 2014-04-03 |
CN108064067A (en) | 2018-05-22 |
US11363647B2 (en) | 2022-06-14 |
EP2811767B1 (en) | 2020-11-11 |
US20170230895A1 (en) | 2017-08-10 |
CN103716761B (en) | 2018-05-11 |
CN103716761A (en) | 2014-04-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11363647B2 (en) | Method for controlling connection between user equipment and network, and mobility management entity | |
US9674830B2 (en) | Method for processing data associated with session management and mobility management | |
US10616868B2 (en) | Method for connecting IMS-based service | |
EP3422797B1 (en) | Method and user equipment for requesting connection to network | |
EP2805458B1 (en) | Control method and device based on multiple priorities in wireless communication system | |
KR101573156B1 (en) | Method for processing data associated with idle mode signaling reduction in a wireless communication system | |
EP2905990A1 (en) | Method and device for controlling multipriority in wireless communication system | |
US20150195809A1 (en) | Method for processing data associated with location area update in a wireless communication system | |
US9860783B2 (en) | Congestion state reporting method and access network device | |
WO2011138288A1 (en) | Overload control in a packet mobile communication system | |
US20160088545A1 (en) | A node and method for small data communications | |
EP2805436A1 (en) | Control method and device based on multiple priorities in wireless communication system | |
WO2016178373A1 (en) | Mobility management exchange, communication system, and communication control method | |
CN102025596B (en) | Processing method of route optimization, and device as well as communication system thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20140902 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
RA4 | Supplementary search report drawn up and despatched (corrected) |
Effective date: 20150707 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 8/00 20090101AFI20150701BHEP Ipc: H04W 76/02 20090101ALN20150701BHEP Ipc: H04W 28/02 20090101ALI20150701BHEP Ipc: H04W 48/06 20090101ALI20150701BHEP Ipc: H04W 4/00 20090101ALN20150701BHEP |
|
DAX | Request for extension of the european patent (deleted) | ||
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20170831 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: HUAWEI DEVICE (SHENZHEN) CO., LTD. |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: HUAWEI DEVICE CO., LTD. |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602013074036 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04W0008000000 Ipc: H04W0008060000 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 48/06 20090101ALI20200428BHEP Ipc: H04W 76/18 20180101ALN20200428BHEP Ipc: H04W 4/70 20180101ALN20200428BHEP Ipc: H04W 8/06 20090101AFI20200428BHEP Ipc: H04W 28/02 20090101ALI20200428BHEP |
|
INTG | Intention to grant announced |
Effective date: 20200528 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1334616 Country of ref document: AT Kind code of ref document: T Effective date: 20201115 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602013074036 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20201111 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1334616 Country of ref document: AT Kind code of ref document: T Effective date: 20201111 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210211 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210311 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210212 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210311 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210211 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602013074036 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 |
|
26N | No opposition filed |
Effective date: 20210812 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20210228 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210228 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210228 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210228 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210228 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210311 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210228 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20130228 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20231229 Year of fee payment: 12 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201111 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20231229 Year of fee payment: 12 Ref country code: GB Payment date: 20240108 Year of fee payment: 12 |