WO2013151246A1 - 이중 우선순위 어플리케이션을 갖는 기계 형태 통신 장치에 대한 접속 제어 방법 및 장치 - Google Patents
이중 우선순위 어플리케이션을 갖는 기계 형태 통신 장치에 대한 접속 제어 방법 및 장치 Download PDFInfo
- Publication number
- WO2013151246A1 WO2013151246A1 PCT/KR2013/002065 KR2013002065W WO2013151246A1 WO 2013151246 A1 WO2013151246 A1 WO 2013151246A1 KR 2013002065 W KR2013002065 W KR 2013002065W WO 2013151246 A1 WO2013151246 A1 WO 2013151246A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- priority
- mobility management
- low access
- access priority
- Prior art date
Links
Images
Classifications
-
- 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]
Definitions
- the present invention relates to a method for controlling access to a machine type communication (MTC) device having a dual priority application in a mobile communication network.
- MTC machine type communication
- Machine Type Communication is a form of data communication that refers to machine-to-machine (M2M) communication, where one or more entities do not or require minimal human interaction.
- a user equipment (UE) used for MTC may periodically transmit and receive data with an MTC application server through a mobile communication network.
- the terminal used for a plurality of MTC has a characteristic (time tolerant or delay tolerant) that is not sensitive to delay.
- the terminal for the MTC which is not sensitive to delay is processed at a lower priority than the general terminal when processing non-access stratum (NAS) signaling so that the mobile communication service provider can efficiently accommodate a large scale MTC device.
- NAS non-access stratum
- 3GPP 3rd Generation Partnership Project
- 3GPP defines device properties IEs that can be used to handle NAS signaling with low priority and prioritize NAS signaling with low priority when overload occurs in the network. I can refuse to. Configuration information for such low priority NAS signaling may be allocated for each device. That is, the terminal for MTC may be configured to have a low priority or a normal priority.
- the terminal for the MTC when configured to NAS signaling at a low priority, there may occur a case in which the terminal for the MTC needs to access the normal priority in a specific situation. For example, an electric meter may send a report with a lower priority, but when it detects an emergency, such as a device theft, it may want to send an alarm at the normal priority. In such a case, the network may not be able to handle this.
- the present invention has been made to overcome the above-described problem, and in the 3GPP mobile communication network, a terminal for MTC attempts to connect through low priority signaling for periodic data communication, and in certain circumstances, access through normal priority signaling. It aims to provide a way to make it possible.
- An embodiment of the present invention is a signaling method executed in a terminal configured to perform NAS signaling including a low access priority indication in a mobile communication network and configured with indication information indicating that the low access priority may be ignored.
- Another embodiment of the present invention provides a signaling control method executed by a mobility management entity in a mobile communication network, the method comprising: receiving a network registration request including a low access priority from a terminal; Delivering a network registration rejection message including a value for a backoff timer to the terminal; Receiving a network registration request from the terminal that does not include a low access priority or an indication that the network registration request is not low from the terminal while the backoff timer is maintained; Determining whether the terminal is a terminal capable of dual priority operation capable of ignoring low access priority; And if the terminal is a terminal capable of the dual priority operation provides a signaling control method of a mobility management entity comprising the step of performing a network registration procedure.
- Another embodiment of the present invention is a terminal configured to perform NAS signaling with a low access priority in a mobile communication network and configured with indication information indicating that the low access priority can be ignored, wherein the terminal is the low access priority.
- Perform a mobility management or session management procedure including receiving a backoff timer and operating a backoff timer due to mobility management congestion control or session management congestion control, the mobility management without including the low connection priority Or it provides a terminal characterized in that performing a session management procedure.
- Another embodiment of the present invention is a mobility management entity of a mobile communication network, which receives a network registration request including a low access priority from a terminal, and transmits a network registration rejection message including a value for a backoff timer to the terminal. And when receiving a network registration request from the terminal that does not include a low access priority or a network registration request that includes an indication from the terminal that is not a low access priority while the backoff timer is maintained.
- Mobility management including a dual priority management unit that determines whether the dual priority operation capable of ignoring the low access priority is possible, and executes a network registration procedure when the terminal is the terminal capable of the dual priority operation. Provide an object.
- the terminal may attempt to connect through low priority signaling for periodic data communication and may attempt to connect through normal priority signaling for a specific situation. Accordingly, while effectively controlling the overload caused by the terminal, it is possible to perform signaling that does not use low priority in a specific situation such as terminal theft detection.
- FIG. 1 shows an example of a 3GPP system as a structure of a system to which an embodiment of the present invention can be applied.
- FIG 3 is a view for explaining a connection control method according to an embodiment of the present invention.
- FIG. 4 illustrates information or functions included in a network entity according to the above-described embodiment.
- FIG. 1 shows an example of a 3GPP system as a structure of a system to which an embodiment of the present invention can be applied.
- the terminal 100 is a terminal for machine type communication (MTC).
- the terminal 100 may include one or more MTC applications 101.
- the RAN 110 is a wireless access network to which the terminal 100 may access.
- Mobile Switching Center (MSC) 120 is a circuit switched based mobile switch.
- the mobility management entity (MME) 130 is an entity on a control plane for supporting a mobility management function in an evolved packet service (EPS).
- EPS evolved packet service
- the Serving GPRS Support Node (SGSN) 140 is a packet switched based mobile switch that performs mobility management functions and the like.
- S-GW 150 is a gateway that terminates an interface with an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN).
- E-UTRAN Evolved UMTS Terrestrial Radio Access Network
- Gateway GPRS Support Node / PDN GateWay (GGSN / P-GW) 160 is an entity that provides interworking between a General Packet Radio Service (GPRS) network and an external packet-switched network, or a Packet Data Network (PDN). This is the gateway that terminates the interface.
- GPRS General Packet Radio Service
- PDN Packet Data Network
- SCS 170 is an entity used to communicate with the terminal 100 for MTC, the MTC-IWF (180) of the Home Public Land Mobile Network (HPLMN) for device triggering or It is connected with the SMS-SC 210.
- SCS 170 may be used by one or more MTC applications.
- Machine Type Communication InterWorking Function (MTC-IWF) 180 functions to relay or translate a signaling protocol used to operate a specific function in a mobile communication network through an interface (Tsp) with the SCS 170.
- Tsp interface
- the home subscriber server (HSS) 190 is a master database for a user, and includes an subscription related information necessary to support session processing for a network entity.
- the CDF / CGF (Charging Data Function / Charging Gateway Function) 200 is an entity that performs a function for charging.
- the SMS-SC / GMSC / IW MSC (Short Message Service-Service Center / Gateway Mobile Switching Center / InterWorking Mobile Switching Center) 210 is an entity for providing a short message service between entities that transmit and receive a short message.
- IP-SM-GW IP Short Message Gate Way 220 performs a message conversion function between the SMS message and the IP message.
- the short message entity (SME) 230 is an entity that transmits and receives a short message.
- the short message entity 230 may be a terminal or an SCS 170.
- AS Application Server (240-1, 240-2) is the entity where the MTC application of the external network is hosted.
- the MTC application 101 in the terminal 100 and the ASs 240-1 and 240-2 of the external network may be connected in various ways.
- the indirect model is defined by the AS 240-1 in order for the AS 240-1 to perform indirect user plane communication with the terminal 100 or to use an additional service such as device triggering. It is a model for indirectly connecting to a network through a service of the SCS 170.
- the direct model is a model in which the AS 240-2 directly connects to the network without passing through the SCS 170.
- Hybrid model indicates that the AS uses the direct and indirect models simultaneously.
- the terminal 100 may be configured with a low access priority or may be configured with an Open Mobile Alliance (OMA) DM ( Device Management (US) or Universal Subscriber Identity Module (USIM) can be configured through an over-the-air (OTA) procedure.
- OMA Open Mobile Alliance
- DM Device Management
- USIM Universal Subscriber Identity Module
- OTA over-the-air
- the low priority NAS signaling configuration included in the USIM is defined in 3GPP TS 24.368.
- the UE configured for low access priority 100 including the low priority indication according to the configuration of the terminal 100 includes device properties information element in the NAS signaling message. It can indicate that this is configured with a low connection priority.
- Table 1 describes the contents of the device attribute information.
- the first 1 bit of all 8 bits of the device attribute information is used to indicate priority. If the value of the first bit is 0, the UE is not set to NAS signaling low priority (ie, it is usually priority). If the value of the first bit is 1, the terminal is set to NAS signaling low priority. Bits 2 through 4 are left blank, and bits 5 through 8 are assigned an information element identifier (IEI) to indicate that the information is for device characteristics.
- IEEEI information element identifier
- the terminal 100 configured with the low access priority should transmit the MME 130 and the low access priority indication (set the above device attribute information to 1) during the NAS signaling procedure.
- the RRC (Radio Resource Control) connection establishment procedure with 111) the RRC establishment cause may be transmitted by indicating a low access priority with 'Delay tolerant'.
- NAS level mobility management congestion control is composed of general NAS level mobility management congestion control (subscription) and subscribed APN based congestion control (APN) based congestion control (APN).
- the network may reject a mobility management NAS signaling request (eg, an attach request) from the terminal.
- a mobility management NAS signaling request eg, an attach request
- the network may reject the NAS signaling message including the low priority indication before rejecting the NAS signaling message that does not include the low priority indication.
- the network may reject the network registration request from the terminal subscribed to this APN.
- the network may send a value for the mobility management back-off timer (T3346 timer) to the terminal in the reject message, and the terminal may include a value included in the mobility management reject message. And start the T3346 backoff timer.
- T3346 timer the mobility management back-off timer
- the terminal While the mobility management backoff timer is running, the terminal cannot initiate a NAS request for the mobility management procedure except for some specific circumstances. This particular situation may be a detach procedure, a service user with a particular access class, an emergency service, or a mobile incoming service.
- the MME 130 may include a session management backoff timer to reject.
- congestion control for the APN is activated, the MME 130 may store a session management backoff timer for each terminal 100.
- the terminal 100 receives the session management backoff timer in the EPS session management reject message, the terminal cannot initiate the session management procedure until the EPS session management backoff timer expires.
- the application server 240 that normally requires priority access, except in certain cases, is applied to the application server 240. Can't communicate with
- a terminal configured to perform NAS signaling including a low priority indication may be applied to an application requiring normal priority access even when the backoff timer is operating due to the overload control as described above.
- the UE may override the low priority NAS signaling configuration and perform NAS signaling including the normal priority indication (the device attribute information is set to 0).
- FIG 3 is a view for explaining a connection control method according to an embodiment of the present invention.
- the network may define subscription information for the operation to check whether the operation is allowed based on the subscription.
- the subscription information in the HSS 190 with an indication that the terminal 100 used for the MTC supports dual priority applications, the MTC application server
- the UE 100 configured to perform NAS signaling including low priority when performing regular communication with the UE or performing a general mobility management procedure, and perform NAS signaling including a low priority indication.
- the terminal 100 configured to perform NAS signaling including low priority does not include the NAS signaling without including the low priority indication. You can configure it for NAS Signaling Low Priority Overriding.
- the subscription information may further include a criterion (eg, application information, MTC-IWF information, AS information, SCS information, etc.) for NAS signaling without including a low priority indication.
- the terminal 100 may perform NAS signaling including a low priority indication. However, in the above-described specific situation, NAS signaling may be performed without including a low priority indication.
- the MME 130 may check whether the terminal 100 allows NAS signaling that does not include a low priority by querying subscription information of the HSS 190. To this end, the MME 130 may maintain the above-mentioned subscription information in the terminal context information.
- the MME 130 Send a reject message to the low priority terminal 100, and the terminal 100 starts a mobility management backoff timer.
- NAS signaling may be performed without including the low priority even while the backoff timer is operated by the low priority NAS signaling.
- NAS signaling may be initiated by an application 101-1 or 101-2.
- the terminal 100 may stop the mobility management backoff timer and initiate NAS signaling. Alternatively, the terminal 100 may maintain a mobility management backoff timer and initiate NAS signaling.
- the low priority indication is displayed by the normal priority application.
- the terminal 100 which does not include the NAS signaling does not include the reason for establishing the RRC for the NAS signaling described above as 'MO data' or 'MO signaling' instead of 'delay tolerant' even during the RRC connection establishment procedure with the base station 111. It can usually communicate that the mobile outgoing connection indication.
- the MME 130 checks whether the terminal 100 supports the dual priority to enable NAS signaling without including a low priority indication in a specific situation. If the mobility management backoff timer is determined to be a terminal capable of NAS signaling without including a low priority indication, the MME 130 may release the mobility management backoff timer and perform the NAS signaling procedure. Can be. Alternatively, the MME 130 may maintain a mobility management backoff timer and perform a NAS signaling procedure.
- the terminal 100 While the session management backoff timer (eg T3396 timer) is operated by NAS signaling with a low priority indication, the terminal 100 has a low priority by an application capable of NAS signaling without including the low priority indication.
- the MME 130 When passing a NAS session management request message (with the device attribute information set to 0 above) not including a low priority indication to establish a new PDN connection that does not contain an indication, the MME 130 sends an S-GW 150.
- the Create Session Request message to the P-GW 160 may be delivered without including a low priority indication, or may include an indication indicating that the P-GW 160 is not low priority.
- the priority associated with the PDN connection does not change until the PDN connection is deactivated.
- the terminal 100 may have a low priority by an application capable of NAS signaling without including the low priority indication.
- the terminal 100 sets a session management backoff timer. Stop and forward a NAS session management request message that does not include a low priority indication, the MME 130 releases the session management backoff timer and creates a Create Session Request to the S-GW 150 or P-GW 160.
- the message may be delivered without including a low priority indication, or with an indication indicating that it is not a low priority.
- This priority indication may be included in the billing record at home and visited networks. For this purpose, the priority indication may need to be stored in the EPS bearer context of the MME 130.
- the terminal 100 When the terminal 100 is configured by EAB (Extended Access Barring) by the operator, such a terminal 100 may be blocked.
- EAB Extended Access Barring
- the terminal 100 indicates that the dual priority operation is configured to enable information, that is, a terminal configured with NAS signaling low priority overrides the NAS signaling low priority, and the NAS signaling with normal Priority Define the information indicating that the terminal is configured to configure the terminal 100 (eg NAS Signaling Low Priority Overriding) and the terminal 100 transmits a priority indication according to this configuration information to the network to the normal priority in the network Can be handled with
- the above priority indication indicates that the terminal configured to perform NAS signaling including the low priority overrides the low priority NAS signaling configuration by the terminal by an application requiring a normal priority connection and marks it as normal priority. (The above-mentioned device attribute information is set to 0).
- the terminal 100 may be preconfigured to support dual priority applications or may be configured through an OMA DM or USIM OTA procedure.
- the terminal 100 configured to support the dual priority application transmits a NAS signaling message including a low priority indication in the device attribute information in the NAS message when performing regular data communication or performing a general mobility management procedure. can do.
- the MME 130 Send a reject message to the low priority terminal 100, and the terminal 100 starts a mobility management backoff timer.
- NAS signaling may be performed without including the low priority while the backoff timer is operated by the low priority NAS signaling.
- NAS signaling may be initiated by the applications 101-1 and 101-2.
- the NAS signaling message may include a priority indication (setting the device attribute information to 0) according to the dual priority support configuration described above.
- the terminal 100 may stop the mobility management backoff timer and initiate NAS signaling. Alternatively, the terminal 100 may maintain a mobility management backoff timer and initiate NAS signaling.
- NAS Signaling Low Priority Overriding NAS Signaling Low Priority Overriding
- the MME 130 may determine whether the terminal 100 supports the dual priority and is a terminal capable of NAS signaling without including a low priority indication in a specific situation. If the mobility management backoff timer is determined to be a terminal capable of NAS signaling without including a low priority indication, the MME 130 may release the mobility management backoff timer and perform the NAS signaling procedure. Can be. Alternatively, the MME 130 may maintain a mobility management backoff timer and perform a NAS signaling procedure. Alternatively, the MME 130 may support the dual priority and perform the NAS signaling procedure without checking whether the UE is capable of NAS signaling without including a low priority indication in a specific situation.
- the terminal 100 While the session management backoff timer is operating by NAS signaling with a low priority indication, the terminal 100 does not include a low priority indication by an application capable of NAS signaling without including the low priority indication.
- the MME 130 When forwarding a NAS session management request message (with the device attribute information set to 0 above) not including a low priority indication to establish a new PDN connection, the MME 130 will either send the S-GW 150 or the P-GW.
- the Create Session Request message to the 160 may be delivered without including a low priority indication, or may include an indication indicating that the message is not a low priority.
- the priority associated with the PDN connection does not change until the PDN connection is deactivated.
- the terminal 100 may have a low priority by an application capable of NAS signaling without including the low priority indication.
- the terminal 100 sets a session management backoff timer.
- Stop or maintain the NAS session management request message (set the device attribute information above to 0) that does not include a low priority indication, and the MME 130 disables or maintains the session management backoff timer; Create Session Request messages sent to S-GW 150 or P-GW 160 without including a low priority indication, or low priority It may include an indication indicating that is not.
- This priority indication may be included in the billing record at home and visited networks. For this purpose, the priority indication may need to be stored in the EPS bearer context of the MME 130.
- the terminal 100 When the terminal 100 is configured by EAB (Extended Access Barring) by the operator, such a terminal 100 may be blocked.
- EAB Extended Access Barring
- the terminal 100 and the network may have new control procedures for dual applications in the network in addition to the existing processing procedures for low priority NAS signaling.
- the terminal 100 configured to perform NAS signaling with a low priority includes a low priority indication in the device attribute information in the NAS message when performing regular data communication or when performing a general mobility management procedure.
- a signaling message can be sent.
- the MME 130 Send a reject message to the low priority terminal 100, and the terminal 100 starts a mobility management backoff timer.
- the terminal 100 configured to perform NAS signaling including the low priority may be NAS by the applications 101-1 and 101-2 capable of NAS signaling without including the low priority while the backoff timer is operating. Signaling may be initiated.
- the NAS signaling message may include a priority indication according to the dual priority support configuration described above.
- the terminal 100 may stop the mobility management backoff timer and initiate NAS signaling.
- the terminal 100 may maintain a mobility management backoff timer and initiate NAS signaling.
- the terminal 100 may transmit a signaling message including an indication that does not include the low priority or does not include the low priority.
- the terminal 100 for initiating NAS signaling that does not include a low priority indication by the normal priority application, the base station ( 111) and the RRC establishment reason for the NAS signaling described above during the RRC connection establishment procedure, it is possible to convey the mobile outgoing access indication as 'MO data' or 'MO signaling' instead of 'delay tolerant'.
- the MME 130 When the MME 130 transmits the NAS signaling message including the indication that is not the low priority, when the terminal 100 which initiated the NAS signaling including the low priority indication, the MME 130 takes into account the network overload status and the operator setting. It can handle NAS signaling messages that contain indications that are not low priority. For example, when the terminal 100 which started the NAS signaling including the low priority indication according to the operator setting transmits the NAS signaling message including the non-low priority indication within three times during the operation of the backoff timer.
- the MME 130 may be configured to process up to three NAS signaling messages. MME 130 may release the mobility management backoff timer and perform the NAS signaling procedure. Alternatively, the MME 130 may maintain a mobility management backoff timer and perform a NAS signaling procedure.
- the terminal 100 While the session management backoff timer is operating by NAS signaling with a low priority indication, the terminal 100 does not include a low priority indication by an application capable of NAS signaling without including the low priority indication.
- the MME 130 When forwarding a NAS session management request message (with the device attribute information set to 0 above) not including a low priority indication to establish a new PDN connection, the MME 130 will either send the S-GW 150 or the P-GW.
- the Create Session Request message to the 160 may be delivered without including a low priority indication, or may include an indication indicating that the message is not a low priority.
- the priority associated with the PDN connection does not change until the PDN connection is deactivated.
- the terminal 100 may have a low priority by an application capable of NAS signaling without including the low priority indication.
- the terminal 100 sets a session management backoff timer. Stop and forward a NAS session management request message that does not include a low priority indication, the MME 130 maintains a session management backoff timer and creates a Create Session Request to the S-GW 150 or P-GW 160.
- the message may be delivered without including a low priority indication, or with an indication indicating that it is not a low priority.
- a PDN connection When a PDN connection is established, the priority associated with the PDN connection does not change until the PDN connection is deactivated.
- This priority indication may be included in the billing record at home and visited networks. For this purpose, the priority indication may need to be stored in the EPS bearer context of the MME 130.
- the terminal 100 When the terminal 100 is configured by EAB (Extended Access Barring) by the operator, such a terminal 100 may be blocked.
- EAB Extended Access Barring
- FIG. 4 illustrates information or functions included in a network entity according to the above-described embodiment.
- the terminal 100 may include information 105 indicating dual priority support of low priority and normal priority, and / or the MME 130 may signal that is not low priority.
- the terminal 100 that transmits the information may include a dual priority control function 135 that may determine whether the terminal supports dual priority and perform control accordingly, and / or the HSS 190 may include Subscriber information including information 195 on whether dual priority is supported may be stored and provided to other entities.
- the terminal 100 indicates that the dual priority operation is configured to enable information, that is, the terminal configured with NAS signaling low priority overrides the NAS signaling low priority, the NAS as a normal Priority Define the information indicating that the terminal is configured to enable signaling (eg NAS Signaling Low Priority Overriding) and configured in the network (eg NAS Signaling Low Priority Overriding), the network according to the NAS signaling priority requested by the UE NAS level mobility management congestion control and / or APN PDN connection will be described in case of congestion control based on mobility management.
- signaling eg NAS Signaling Low Priority Overriding
- the network eg NAS Signaling Low Priority Overriding
- the terminal 100 configured to enable the dual priority operation that is, the terminal configured to allow the NAS signaling low priority configured to override the NAS signaling low priority (eg UE configured for dual priority or UE configured for NAS signaling Low Priority Overriding) supports dual-priority applications, and is pre-configured to allow the UE to override NAS signaling low priority by normal priority applications and to perform NAS signaling with normal priority, OMA DM or It can be configured through the USIM OTA procedure.
- the terminal configured to allow the NAS signaling low priority configured to override the NAS signaling low priority eg UE configured for dual priority or UE configured for NAS signaling Low Priority Overriding
- supports dual-priority applications and is pre-configured to allow the UE to override NAS signaling low priority by normal priority applications and to perform NAS signaling with normal priority, OMA DM or It can be configured through the USIM OTA procedure.
- the terminal 100 configured to support the dual priority application includes a low priority indication in the device attribute information in the NAS message when performing regular data communication by a low priority application or when performing a general mobility management procedure.
- NAS signaling message can be transmitted.
- the terminal 100 configured to support the dual priority application does not include the low priority and the terminal 100 does not include the low priority by the applications 101-1 and 101-2 to be NAS-signaled ( NAS signaling may be initiated by setting the device attribute information to zero.
- the terminal 100 configured to support dual priority applications performs NAS signaling with low priority.
- the MME 130 Forwards the low priority indication in the Create Session Request message to the S-GW 150 or the P-GW 160.
- the priority associated with the PDN connection does not change until the PDN connection is deactivated.
- the low priority indication is stored in the MME EPS bearer context.
- the terminal 100 configured to support the dual priority application does not include the low priority, but the terminal 100 includes the low priority by the applications 101-1 and 101-2 that want to perform NAS signaling.
- the network supports multiple PDN connections by operator policy and the UE subscribes to multiple PDNs. (subscriptions), the terminal 100 may request a new PDN connection through a NAS session management request message (PDN connectivity request message) that does not include a low priority indication. That is, when the terminal 100 has a subscription for the APN for the PDN connection including the low priority indication and the APN for the PDN connection not including the low priority indication, the terminal 100 indicates the low priority indication.
- PDN connectivity request message NAS session management request message
- a new PDN connection may be requested through a NAS session management request message (PDN connectivity request message) that does not include a message.
- PDN connectivity request message NAS session management request message
- the terminal 100 transmits to the MME including the APN in the PDN connection request that does not include the low priority indication.
- the PDN connection connection not including the low priority indication may be additionally provided to the PDN connection connection including the low priority indication.
- a PDN connection connection not including the low priority indication may be provided by deactivating the PDN connection connection including the low priority indication (e.g. detach).
- the terminal 100 includes a low priority indication If the terminal 100 does not have a subscription to the dedicated APN for the PDN connection that does not, the terminal 100 deactivates (eg detaches) an existing PDN connection including a low priority indication (eg detach) and establishes a new PDN connection.
- the PDN connectivity request message for the bearer establishment in attach procedure in the network registration procedure does not include a low priority indication (the device attribute information described above is zero).
- the MME 130 forwards that the Create Session Request message to the S-GW 150 or the P-GW 160 does not include a low priority indication (setting the above device attribute information to 0). .
- a low priority indication setting the above device attribute information to 0.
- the priority associated with the PDN connection does not change until the PDN connection is deactivated.
- the low priority indication is stored in the MME EPS bearer context.
- the low priority indication is indicated by the normal priority application.
- the terminal 100 for initiating NAS signaling that does not include the RRC establishment reason for the above-described NAS signaling even during the RRC connection establishment procedure with the base station 111 is 'MO data' or 'MO signaling' instead of 'delay tolerant'. In this case, the mobile outgoing connection indication can be delivered.
- the terminal 100 configured to support the dual priority application does not include the low priority and does not include the low priority by the applications 101-1 and 101-2 that want to perform NAS signaling (
- the device attribute information is set to 0
- the NAS signaling when the NAS signaling is to be initiated, whether the network supports multiple PDN connections according to an operator policy or whether the UE subscribes to multiple PDNs.
- NAS signaling may be initiated that does not include the low priority as described above (set the device attribute information to zero).
- the UE in the idle state, the UE first attempts to use an available PDN connection by initiating a service request procedure including a low priority indication and may be controlled by NAS level mobility management congestion control or APN-based mobility management congestion control. For the case of receiving a reject message from the network, it is possible to initiate NAS signaling not including the low priority as described above (setting the device attribute information to zero above).
- the terminal 100 configured to support the dual priority application does not include the low priority and the terminal 100 does not include the low priority by the applications 101-1 and 101-2 to be NAS-signaled (
- the device attribute information is set to 0
- the NAS signaling request message is transmitted, mobility management signaling congestion in the network or APN-based mobility management congestion control subscribed to a specific APN or EPS session management associated with a specific APN (EPS Session).
- ESM Management
- congestion control is activated, when receiving a reject message including a mobility management backoff timer or a session management backoff timer from the network, the terminal backs off with a backoff timer value provided through the reject message Start the timer.
- the UE causes the backoff timer to indicate that the NAS signaling request message does not include a low priority indication. You can set or save the value (cause). The backoff timer trigger cause value may be removed when the backoff timer expires.
- the network may send the rejection message with a low priority indication of the NAS signaling request message that caused the rejection message or is associated with the rejection message.
- a cause value can be defined in an EMM cause or a new information element (IE) can be added.
- the terminal may set or store the low priority indication information included in the reject message together with the backoff timer.
- the terminal 100 may initiate a NAS signaling request except for some specific situations described above such as an emergency service. none.
Abstract
Description
Claims (14)
- 이동 통신망에서 낮은 접속 우선순위 표시를 포함하여 NAS 시그널링을 하도록 구성되고, 상기 낮은 접속 우선순위를 무시할 수 있음을 나타내는 표시 정보가 구성된 단말에서 실행되는 시그널링 방법으로서,상기 낮은 접속 우선순위를 포함하여 이동성 관리 또는 세션 관리 프로시저를 수행하는 단계;이동성 관리 폭주 제어 또는 세션 관리 폭주 제어로 인해 백오프 타이머를 수신하고, 백오프 타이머를 동작시키는 단계; 및상기 낮은 접속 우선순위를 포함하지 않고 상기 이동성 관리 또는 세션 관리 프로시저를 수행하는 단계를 포함하는 단말의 시그널링 방법.
- 제 1 항에 있어서,상기 낮은 접속 우선순위를 포함하지 않고 상기 이동성 관리 또는 세션 관리 프로시저를 수행하는 단계는, 상위 계층 응용의 요청에 의해 개시되는 것을 특징으로 하는 단말의 시그널링 방법.
- 제 1 항에 있어서,상기 낮은 접속 우선순위를 포함하지 않고 상기 이동성 관리 또는 세션 관리 프로시저를 수행하는 단계는, 기지국으로의 RRC 연결 성립 이유를 'MO signaling' 또는 'MO data'로 하는 것을 특징으로 하는 단말의 시그널링 방법.
- 제 1 항에 있어서,상기 낮은 접속 우선순위를 포함하여 이동성 관리 또는 세션 관리 프로시저를 수행하는 단계는, 기지국으로의 RRC 연결 성립 이유를 'delay tolerant'로 하는 것을 특징으로 하는 단말의 시그널링 방법.
- 제 1항에 있어서상기 낮은 접속 우선순위를 포함하지 않고 상기 이동성 관리 또는 세션 관리 프로시저를 수행하는 단계 이후 이동성관리 개체에 의해 이동성 관리 폭주 제어 또는 세션 관리 폭주 제어로 인해 백오프 타이머를 수신하는 경우, 이동성관리개체로부터 수신된 백오프 타이머 값으로 백오프타이머를 시작하는 단계를 더 포함하는 단말의 시그널링 방법.
- 이동 통신망에서 이동성 관리 개체의 의해 실행되는 시그널링 제어 방법으로서,단말로부터 낮은 접속 우선순위를 포함하는 네트워크 등록 요청을 수신하는 단계;백오프 타이머를 위한 값을 포함하는 네트워크 등록 거부 메시지를 상기 단말로 전달하는 단계;상기 백오프 타이머가 유지되는 동안 상기 단말로부터 낮은 접속 우선순위를 포함하지 않는 네트워크 등록 요청 또는 상기 단말로부터 낮은 접속 우선순위가 아님을 나타내는 표시를 포함하는 네트워크 등록 요청을 수신하는 단계;상기 단말이 낮은 접속 우선순위를 무시할 수 있는 이중 우선순위 동작이 가능한 단말인지 여부를 판단하는 단계; 및상기 단말이 상기 이중 우선순위 동작이 가능한 단말인 경우 네트워크 등록 절차를 실행하는 단계를 포함하는 이동성 관리 개체의 시그널링 제어 방법.
- 제 6 항에 있어서,상기 이중 우선순위 동작이 가능한 단말인지 여부를 판단하는 단계는 가입자 정보 서버에 상기 단말이 상기 이중 우선순위 동작이 가능한 단말인지 여부를 조회하는 단계를 포함하는 것을 특징으로 하는 이동성 관리 개체의 시그널링 제어 방법.
- 이동 통신망에서 낮은 접속 우선순위를 가지고 NAS 시그널링을 하도록 구성되고, 상기 낮은 접속 우선순위를 무시할 수 있음을 나타내는 표시 정보가 구성된 단말로서,상기 단말은 상기 낮은 접속 우선순위를 포함하여 이동성 관리 또는 세션 관리 프로시저를 수행하며, 이동성 관리 폭주 제어 또는 세션 관리 폭주 제어로 인해 백오프 타이머를 수신하고 백오프 타이머를 동작시키며, 상기 낮은 접속 우선순위를 포함하지 않고 상기 이동성 관리 또는 세션 관리 프로시저를 수행하는 것을 특징으로 하는 단말.
- 제 8 항에 있어서,상기 낮은 접속 우선순위를 포함하지 않고 상기 이동성 관리 또는 세션 관리 프로시저를 수행하는 것은 상위 계층 응용의 요청에 의해 개시되는 것을 특징으로 하는 단말.
- 제 8 항에 있어서,상기 낮은 접속 우선순위를 포함하지 않고 상기 이동성 관리 또는 세션 관리 프로시저를 수행할 때, 기지국으로의 RRC 연결 성립 이유를 'MO signaling' 또는 'MO data'로 하는 것을 특징으로 하는 단말.
- 제 8항에 있어서,상기 낮은 접속 우선순위를 포함하여 이동성 관리 또는 세션 관리 프로시저를 수행할 때, 기지국으로의 RRC 연결 성립 이유를 'delay tolerant'로 하는 것을 특징으로 하는 단말.
- 제 8 항에 있어서상기 낮은 접속 우선순위를 포함하지 않고 상기 이동성 관리 또는 세션 관리 프로시저를 수행하는 단계 이후 이동성관리 개체에 의해 이동성 관리 폭주 제어 또는 세션 관리 폭주 제어로 인해 백오프 타이머를 수신하는 경우, 이동성관리개체로부터 수신된 백오프 타이머 값으로 백오프타이머를 시작하는 것을 특징으로 하는 단말.
- 이동 통신망의 이동성 관리 개체로서,단말로부터 낮은 접속 우선순위를 포함하는 네트워크 등록 요청을 수신하고, 백오프 타이머를 위한 값을 포함하는 네트워크 등록 거부 메시지를 상기 단말로 전달하며, 상기 백오프 타이머가 유지되는 동안 상기 단말로부터 낮은 접속 우선순위를 포함하지 않는 네트워크 등록 요청 또는 상기 단말로부터 낮은 접속 우선순위가 아님을 나타내는 표시를 포함하는 네트워크 등록 요청을 수신할 때, 상기 단말이 낮은 접속 우선순위를 무시할 수 있는 이중 우선순위 동작이 가능한 단말인지 여부를 판단하고, 상기 단말이 상기 이중 우선순위 동작이 가능한 단말인 경우 네트워크 등록 절차를 실행하는 이중 우선순위 관리부를 포함하는 이동성 관리 개체.
- 제 13 항에 있어서,상기 이중 우선순위 관리부는 가입자 정보 서버에 상기 단말이 상기 이중 우선순위 동작이 가능한 단말인지 여부를 조회하는 것을 특징으로 하는 이동성 관리 개체.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/389,414 US9386478B2 (en) | 2012-04-04 | 2013-03-14 | Method and apparatus for controlling access to machine-type communication device having dual priority application |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR20120035116 | 2012-04-04 | ||
KR10-2012-0035116 | 2012-04-04 | ||
KR10-2012-0055238 | 2012-05-24 | ||
KR20120055238 | 2012-05-24 | ||
KR10-2012-0098705 | 2012-09-06 | ||
KR1020120098705A KR101565102B1 (ko) | 2012-04-04 | 2012-09-06 | 이중 우선순위 어플리케이션을 갖는 기계 형태 통신 장치에 대한 접속 제어 방법 및 장치 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013151246A1 true WO2013151246A1 (ko) | 2013-10-10 |
Family
ID=49300696
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2013/002065 WO2013151246A1 (ko) | 2012-04-04 | 2013-03-14 | 이중 우선순위 어플리케이션을 갖는 기계 형태 통신 장치에 대한 접속 제어 방법 및 장치 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2013151246A1 (ko) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018131970A1 (ko) * | 2017-01-15 | 2018-07-19 | 엘지전자 주식회사 | 네트워크에서 혼잡이 발생한 경우 혼잡을 제어하는 방법 |
CN110167202A (zh) * | 2019-04-26 | 2019-08-23 | 维沃移动通信有限公司 | 会话处理方法、装置、终端及介质 |
CN112888018A (zh) * | 2021-01-22 | 2021-06-01 | Oppo广东移动通信有限公司 | 一种注网方法及终端设备 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20040048568A (ko) * | 2002-12-04 | 2004-06-10 | 엘지전자 주식회사 | 이동 통신 시스템에서 과부하 제어 장치 및 방법 |
KR20050076158A (ko) * | 2004-01-19 | 2005-07-26 | 삼성전자주식회사 | 트래픽 폭주 제어 방법 및 이를 구현하기 위한 장치 |
-
2013
- 2013-03-14 WO PCT/KR2013/002065 patent/WO2013151246A1/ko active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20040048568A (ko) * | 2002-12-04 | 2004-06-10 | 엘지전자 주식회사 | 이동 통신 시스템에서 과부하 제어 장치 및 방법 |
KR20050076158A (ko) * | 2004-01-19 | 2005-07-26 | 삼성전자주식회사 | 트래픽 폭주 제어 방법 및 이를 구현하기 위한 장치 |
Non-Patent Citations (2)
Title |
---|
HUAWEI ET AL.: "EAB for E-UTRAN", 3GPP SA WG2 MEETING #89 S2-121057, 10 February 2012 (2012-02-10), VANCOUVER, CANADA * |
RAHUL, VAIDYA ET AL.: "Network congestion control: mechanisms for congestion avoidance and recovery", ACWR ' 11 PROCEEDINGS OF THE 1 ST INTERNATIONAL CONFERENCE ON WIRELESS TECHNOLOGIES FOR HUMANITARIAN RELIEF, November 2011 (2011-11-01), pages 199 - 207 * |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018131970A1 (ko) * | 2017-01-15 | 2018-07-19 | 엘지전자 주식회사 | 네트워크에서 혼잡이 발생한 경우 혼잡을 제어하는 방법 |
US10999779B2 (en) | 2017-01-15 | 2021-05-04 | Lg Electronics Inc. | Method for controlling congestion when congestion occurs in network |
CN110167202A (zh) * | 2019-04-26 | 2019-08-23 | 维沃移动通信有限公司 | 会话处理方法、装置、终端及介质 |
CN110167202B (zh) * | 2019-04-26 | 2021-04-20 | 维沃移动通信有限公司 | 会话处理方法、装置、终端及介质 |
CN112888018A (zh) * | 2021-01-22 | 2021-06-01 | Oppo广东移动通信有限公司 | 一种注网方法及终端设备 |
CN112888018B (zh) * | 2021-01-22 | 2023-07-25 | Oppo广东移动通信有限公司 | 一种注网方法及终端设备 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR101655693B1 (ko) | 이중 우선순위 어플리케이션을 갖는 기계 형태 통신 장치에 대한 접속 제어 방법 및 장치 | |
US11051361B2 (en) | Method for controlling service in radio communication system | |
EP2472790B1 (en) | Method, mobile management unit and gateway for restricting access and communication for a mtc device | |
WO2012134248A2 (en) | Method and apparatus for processing signal associated with warning notification in wireless communication system | |
WO2013028026A2 (en) | Method and apparatus for transmitting uplink data associated with mtc device trigger function | |
WO2013085310A1 (en) | Apparatus and method for delivering short message service efficiently in wireless communication system | |
WO2011159125A2 (ko) | 무선 통신 시스템 및 그의 사용자 단말기와 이동성 관리 엔티티 간 연결 방법 | |
WO2013062325A1 (en) | Method and apparatus for updating extended access barring information | |
WO2013051827A2 (en) | Mobility management entity having mobile switching center functionality | |
WO2011043571A2 (ko) | 무선 통신 시스템에서 m2m 통신을 수행하는 단말의 지역 기반 접근 제어 방법 | |
EP2667665B1 (en) | Controlling access to shared network | |
WO2013109082A1 (ko) | 데이터 전송의 우선권 설정 방법 및 장치 | |
WO2011054299A1 (zh) | 机器类通讯终端信息的获取方法和系统 | |
WO2013172623A1 (ko) | 수신 서비스 페이징 손실을 막는 방법 및 장치 | |
KR20120104959A (ko) | 서빙 코어 네트워크 노드가 변경될 때의 모바일 장치의 접근성의 처리 | |
EP2566201B1 (en) | Machine type communication events report method, device and system | |
WO2013133665A1 (ko) | 무선 통신 시스템의 혼잡 관리를 위한 방법 및 장치 | |
WO2012153969A2 (en) | Method and apparatus for processing data between different layers of mobile station in a wireless communication system | |
WO2014051406A1 (en) | Method for supporting bearer resource control | |
CN101534566A (zh) | 一种寻呼用户的方法、无线接入设备及终端 | |
WO2011029395A1 (zh) | 一种终端的控制方法与装置 | |
WO2013151246A1 (ko) | 이중 우선순위 어플리케이션을 갖는 기계 형태 통신 장치에 대한 접속 제어 방법 및 장치 | |
WO2011050688A1 (zh) | 机器类通讯终端信息的获取方法和系统 | |
WO2015016659A1 (en) | Method and device for proximity discovery among ues | |
JP6160628B2 (ja) | 自律的にimplicitDetach操作を実行するデバイス及び方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13772888 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14389414 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 02/02/2015) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13772888 Country of ref document: EP Kind code of ref document: A1 |