WO2016009578A1 - コネクション管理のための方法および装置 - Google Patents
コネクション管理のための方法および装置 Download PDFInfo
- Publication number
- WO2016009578A1 WO2016009578A1 PCT/JP2015/002418 JP2015002418W WO2016009578A1 WO 2016009578 A1 WO2016009578 A1 WO 2016009578A1 JP 2015002418 W JP2015002418 W JP 2015002418W WO 2016009578 A1 WO2016009578 A1 WO 2016009578A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mtc
- network
- communication
- mtc device
- radio access
- Prior art date
Links
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
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/14—Backbone network devices
Definitions
- the disclosure of this specification relates to a mobile communication network, and particularly to management of a Radio Resource Control (RRC) connection or a Non-Access Stratum (NAS) connection of a Machine Type Communication (MTC) device.
- RRC Radio Resource Control
- NAS Non-Access Stratum
- MTC Machine Type Communication
- MTC Machine Type Communication
- M2M Machine-to-Machine
- 3GPP defines mobile stations (Mobile station (MS), Mobile terminal (MT), User Equipment (UE)) mounted on machines and sensors for MTC as “MTC devices”.
- MTC devices mobile stations (Mobile station (MS), Mobile terminal (MT), User Equipment (UE)) mounted on machines and sensors for MTC as “MTC devices”.
- the MTC device is mounted on various devices such as machines (e.g., firewood vending machines, gas meters, electric meters, automobiles, railway vehicles) and sensors (e.g., fire environment, agriculture, traffic, etc.)
- PLMN Public Land Mobile Network
- AS Application Server
- the MTC application server is arranged outside the PLMN (external network), executes the MTC application, and communicates with the MTC UE application mounted on the MTC device.
- An MTC application server is generally controlled by an MTC service provider (M2M service provider).
- 3GPP provides network elements, reference points, and procedures, including Service Capability Server (SCS) and Machine Type Communication Interworking Functions (MTC-IWF), to enable MTC application servers to communicate with MTC devices.
- SCS Service Capability Server
- MTC-IWF Machine Type Communication Interworking Functions
- a reference point is also called an interface.
- the SCS is an entity that connects the MTC application server to the 3GPP PLMN and enables the MTC application server to communicate with the UE (that is, the MTC device) via the PLMN service defined by 3GPP.
- the SCS also enables the MTC application server to communicate with the MTC-IWF. That is, the SCS provides an application programming interface (Application Programming Interface (API)) to the MTC application server so that the service or capabilities provided by 3GPP PLMN can be used. It is assumed that the SCS is controlled by a PLMN operator or an MTC service provider.
- a framework for mediation that includes one or more SCSs is sometimes referred to as an M2M service platform or an MTC service platform.
- the framework that provides an API to the MTC application server is called an “exposure layer” in Open Mobile Alliance (OMA).
- OMA Open Mobile Alliance
- MTC-IWF is a control plane entity belonging to PLMN.
- MTC-IWF has a signaling interface (reference point) with M2M service platform including SCS, and nodes in PLMN (for example, Home Subscriber Server (HSS), Short Message Service-Service Center (SMS-SC), It has a signaling interface (reference point) to Serving GPRS Support Node (SGSN), Mobility Management Entity (MME), and Mobile Switching Center (MSC).
- the MTC-IWF acts as a control plane interface for the MTC application server or M2M service platform and 3GPP PLMN to interwork while hiding the details of the 3GPP PLMN topology.
- the MTC application server or M2M service platform communicates with the MTC device through 3GPP PLMN.
- the MTC application server or M2M service platform may communicate with the MTC device on the user plane or via a device trigger.
- the inventor of the present case examined various use cases of the MTC application.
- the average communication interval or communication frequency of the MTC device is expected to vary depending on the operation mode, use state, or use environment of the MTC device.
- the communication frequency of the MTC device may change depending on whether the vehicle is running or stopped.
- the communication frequency of the MTC device may change depending on whether or not the auxiliary function related to the Intelligent Transport Systems (ITS) service implemented by the navigation system installed in the vehicle is ON.
- ITS Intelligent Transport Systems
- the communication frequency of the MTC device may be estimated depending on whether or not the vehicle engine is started.
- the communication frequency of the MTC device may change depending on whether the metering device or sensor is in normal operation or abnormal operation.
- the operation mode, usage state, or usage environment of the MTC device may be more easily known in the MTC application server or M2M service platform (eg, SCS) than in the PLMN. .
- MTC application server or the M2M service platform can freely communicate with the MTC device and the user plane (at the application layer) through the PLMN.
- the MTC application server or the M2M service platform may be able to know the usage status and usage environment of the MTC device via a machine on which the MTC device is mounted or other communication means mounted on the sensor.
- the MTC application server or the M2M service platform may be able to know the operation mode, use state, or use environment of the MTC device based on weather or marine alerts announced by government agencies or private organizations.
- Non-Patent Document 1 does not assume such a control operation or control procedure.
- one of the objects to be achieved by the embodiments disclosed in the present specification is to utilize the communication characteristics of the MTC device obtained in the MTC application server or the M2M service platform for managing the connection of the MTC device in the PLMN. Providing a method, an apparatus, and a program that contribute to the performance. Other objects or problems and novel features will become apparent from the description of the present specification or the accompanying drawings.
- a method performed by a mobility management entity located in a core network enables communication characteristics of an MTC device to utilize services provided by a mobile communication network including the core network and a radio access network.
- NAS Stratum
- a method performed by a radio network control entity located in a radio access network can utilize the communication characteristics of the MTC device and the services provided by a mobile communication network including the core network and the radio access network.
- API application programming interface
- a mobility management entity located in the core network includes a memory and a processor coupled to the memory and configured to perform the method according to the first aspect described above.
- a radio network control entity located in the radio access network includes a memory and a processor coupled to the memory and configured to perform the method according to the second aspect described above.
- the program includes a group of instructions (software code) for causing the computer to perform the method according to the first aspect when read by the computer.
- the program includes a group of instructions (software code) for causing the computer to perform the method according to the second aspect described above when read by the computer.
- a method performed by a service capability entity that provides an application programming interface (API) to an MTC application server includes a first message indicating communication characteristics of an MTC device in a network within the core network. Including sending to the entity.
- the first message includes a value of a first inactivity timer (eg, RRC inactivity timer), a value of a second inactivity timer (eg, DRX inactivity timer), and a value of a NAS back-off timer.
- a first inactivity timer eg, RRC inactivity timer
- a second inactivity timer eg, DRX inactivity timer
- a value of a NAS back-off timer causes at least one update.
- a service capability entity that provides an application programming interface (API) to an MTC application server is coupled to the memory and to the memory to perform the method according to the seventh aspect described above. And a configured processor.
- API application programming interface
- the program includes a group of instructions (software code) for causing the computer to perform the method according to the seventh aspect when read by the computer.
- the above-described aspect can provide a method, an apparatus, and a program that contribute to performing connection management of an MTC device in the PLMN using communication characteristics of the MTC device obtained in the MTC application server or the M2M service platform.
- FIG. 1 shows a configuration example of a mobile communication network, that is, a PLMN according to an embodiment of the present invention.
- the mobile communication network provides communication services such as voice communication and / or packet data communication.
- the mobile communication network will be described as EvolvedvolvePacket System (EPS).
- EPS can also be called LongLTerm Evolution (LTE) system or LTE-Advanced system).
- LTE LongLTerm Evolution
- UMTS Universal Mobile Telecommunications System
- the E-UTRAN 110 includes an MTC device (MTC UE) 111 and an eNodeB 112.
- the EPC 120 includes an MME 121, an HSS / Home location register (HLR) 122, an MTC-IWF 123, a Serving gateway (S-GW) 124, and a packet data network (P-GW) 125.
- the M2M service platform 130 includes an SCS 131. As already mentioned, the M2M service platform 130 can also be referred to as an MTC service platform or exposure layer.
- the MTC UE 111 executes the MTC UE application and behaves as an MTC device.
- the MTC UE 111 as the MTC device establishes a signaling connection (that is, a Non-Access Stratum (NAS) connection) with the MME 121 via the E-UTRAN 110, and also uses the MTC application via the S-GW 124 and the P-GW 125. Communicate with the server 132 on the user plane.
- NAS Non-Access Stratum
- the MTC UE 111 may be an MTC gateway device.
- MTC gateway devices have 3GPP mobile communication capabilities (ie UE capabilities) and connect to neighboring devices (eg sensors, radio frequency identification (RFID) tags, car navigation devices) via personal / local area connection technology To do.
- Specific examples of the personal / local area connection technology include IEEE 802.15, ZigBee (registered trademark), Bluetooth (registered trademark), and IEEE 802.11a.
- the neighboring device connected to the MTC gateway device is typically a device that does not have a 3GPP mobile communication function, but may be a device that has a 3GPP mobile communication function (that is, an MTC device). .
- the terms MTC device and MTC gateway device are used without any particular distinction. That is, the term MTC device as used herein encompasses an MTC gateway device.
- the eNodeB 112 establishes a Radio Resource Control (RRC) connection with the MTC UE 111 and sets a signaling radio bearer (Signaling Radio Bearer (SRB)) with the MTC UE 111. Then, the eNodeB 112 performs RRC signaling for setting and modifying the data radio bearer (Data Radio Bearer (DRB)) and NAS message transfer between the EPC 120 (that is, the MME 121) and the MTC UE 111 in the SRB. provide.
- the NAS message is not terminated by the E-UTRAN 110 and is transmitted and received transparently between the MTC UE 111 and the MME 121. Furthermore, the eNodeB 112 transfers the user data of the MTC UE 111 in the DRB with the MTC UE 111.
- the MME 121, the HSS / HLR 122, and the MTC-IWF 123 are control plane nodes or entities.
- the MME 121 performs mobility management and bearer management of a plurality of UEs (UEs) including the MTC-UE 111 attached to the EPC 120 (that is, EMM-REGISTERED-state).
- Mobility management is used to keep track of the UE's current location (keep track) and includes maintaining a mobility management context (MM context) for the UE.
- Bearer management includes controlling the establishment of an EPS bearer for the UE to communicate with an external network (Packet Data Network (PDN)) via the E-UTRAN 110 and the EPC 120 and maintaining an EPS bearer context for the UE.
- PDN Packet Data Network
- HSS / HLR 122 manages subscriber information of UEs including MTC UE 111. In addition, the HSS / HLR 122 records information (such as MME Identity) of the MME that manages each UE attached to the EPC 120 (EMM-REGISTERED state).
- MTC-IWF123 is a control plane entity belonging to EPC120.
- the MTC-IWF 123 communicates with other network entities including the MME 121 and the HSS / HLR 122 via a signaling interface (reference point).
- the MTC-IWF 123 is a control plane interface or gateway for the MTC application server 132 or the M2M service platform 130 and 3GPP PLMN to interwork while hiding the details of the 3GPP PLMN topology. Behave as.
- the MTC-IWF 123 communicates with SCS 131 via a Tsp reference point.
- the SCS 131 connects the MTC application server 132 to the PLMN including the E-UTRAN 110 and the EPC 120 so that the MTC application server 132 can communicate with the MTC UE 111 (that is, the MTC device) via the PLMN service defined by 3GPP.
- the Tsp reference point may be used, for example, for transmitting a device trigger transmission request (Device Trigger Request (DTR)) from the SCS 131 to the MTC-IWF 123 and reporting the device trigger result from the MTC-IWF 123 to the SCS 131.
- DTR Device Trigger Request
- the MTC-IWF 123 communicates with the HSS / HLR 122 via the S6m reference point.
- the S6m reference point may be used, for example, to transmit an inquiry of subscriber information from the MTC-IWF 123 to the HSS / HLR 122 and to transmit subscriber information from the HSS / HLR 122 to the MTC-IWF 123.
- the MTC-IWF 123 communicates with the MME 121 via the T5b reference point.
- the T5b reference point may be used, for example, to transmit a device trigger request from the MTC-IWF 123 to the MME 121 and to report the success or failure of the device trigger from the MME 121 to the MTC-IWF 123.
- the S-GW 124 is a user plane packet transfer node arranged in the EPC 120, and transfers user data packets of the MTC UE 111.
- the S-GW 124 plays a role of a gateway with the E-UTRAN 110.
- the S-GW 124 has a user plane tunneling interface (ie, S1-U reference point) with the E-UTRAN 110, and a user plane tunneling interface (ie, S5 / S8) with the P-GW 125. Reference point).
- the S-GW 124 has a signaling interface (i.e., S11 reference point) with the MME 121.
- the P-GW 125 is a user plane packet transfer node arranged in the EPC 120, as with the S-GW 124, and transfers the user data packet of the MTC UE 111.
- the P-GW 125 plays a role of a gateway with a PDN outside the 3GPP PLMN, and provides connectivity with the PDN to the MTC UE 111.
- the PDN includes an SCS 131 and an application server 132.
- the SCS 131 provides one or more APIs to the MTC application server 132 so that the MTC application server 132 can communicate with the MTC-IWF 123.
- the SCS 131 is controlled by a PLMN operator or an MTC service provider.
- the SCS 131 is also called an MTC server, an M2M server, or an API Gateway Function (API-GWF).
- API-GWF API Gateway Function
- the SCS 131 may communicate with the MTC UE 111 on the user plane or via a device trigger.
- the SCS 131 may be a single independent physical entity or a functional entity added to another network element (for example, the MTC-IWF 123 or the MTC application server 132).
- the MTC application server 132 executes the MTC application and communicates with the MTC UE application installed in the MTC UE 111.
- the MTC application server 132 is also called an M2M application server.
- the mobile communication network (PLMN) including the E-UTRAN 110 and the EPC 120 receives device information indicating the behavior or characteristics of the MTC UE 111 from the M2M service platform 130.
- the device information related to MTC UE 111 indicates the communication characteristics of MTC UE 111.
- the PLMN including the E-UTRAN 110 and the EPC 120 based on the device information of the MTC UE 111 notified from the M2M service platform 130, (a) RRC inactivity timer, (b) DRX inactivity timer, and (c) NAS backoff Update at least one of the timers.
- RRC inactivity timer is used in E-UTRAN 110 (i.e., eNodeB112) to control the timing of MTC UE 111 in the connected state (RRC_CONNECTED state) transitioning to the idle state (RRC_IDLE state).
- RRC inactivity timer is also called IDLE inactivity timer or UE inactivity timer.
- the RRC inactivity timer measures the non-communication period of the MTC UE 111 to determine the state transition from the RRC_CONNECTEDCONNECTstate to the RRC_IDLE state.
- the MTC UE 111 transitions from the RRC_CONNECTED state to the RRC_IDLE state in response to the fact that the non-communication period in the RRC_CONNECTED state has reached a predetermined time, in other words, the RRC inactivity timer has expired.
- the DRX inactivity timer is used in the E-UTRAN 110 (i.e., eNodeB 112) to specify the timing at which the MTC UE 111 starts discontinuous reception (Discontinuous Reception (DRX)) in the connected state (RRC_CONNECTED state).
- DRX inactivity timer measures a non-communication period in order to transition from active mode to DRX mode (sleep mode or dormant mode) in the connected state (RRC_CONNECTED state).
- the DRX mode in the connected state is a state in which the RRC connection between the MTC UE 111 and the eNodeB 112 is maintained, and is different from the idle state (RRC_IDLE state). Therefore, there is a clear distinction between RRCDRinactivity timer and DRX inactivity timer. MTC
- the MTC UE 111 transitions to the DRX mode in the RRC_CONNECTED state in response to the expiration of the DRX inactivity timer, and then transitions to the RRC_IDLE state in response to the expiration of the RRC inactivity timer. That is, the value of RRC inactivity timer is longer than the value of DRX inactivity timer.
- the value of DRX inactivity timer is, for example, about 100 milliseconds. On the other hand, the value of RRC inactivity timer is, for example, about 10 seconds.
- the NAS back-off timer is arranged in the MTC UE 111 and is used for suppressing transmission of uplink NAS messages by the MTC UE 111.
- the NAS back-off timer is called Session-Management-back-off-timer, Mobility-Management-back-off-timer, or Back-off-timer-T3346, etc.
- the MME 121 rejects a NAS request (i.e., SERVICE REQUEST message) related to session management or a NAS request (i.e., TAU REQUEST message) related to mobility management from the MTC UE 111.
- the MTC UE 111 rejected the NAS request activates and detaches the NAS back-off timer, initiates an emergency call, and responds to paging, with a few exceptions. Suppress sending new NAS requests until the NAS back-off timer expires.
- the length of the NAS back-off timer value (ie, back-off time) is specified by the EPC 120.
- the rejection message sent from the MME 121 to the MTC UE 111 to reject the NAS request includes specification of the value of the NAS back-off timer.
- the M2M service platform 130 may transmit device information related to the MTC UE 111 to the MTC-IWF 123. And MTC-IWF123 should just transmit the said device information to MME121 or HSS / HLR122, or both. Further, the device information may be sent to the eNodeB 112 via the MME 121. The device information sent to the MME 121, the HSS / HLR 122, or the eNodeB 112 via the MTC-IWF 123 is at least one of the RRC inactivity timer value, the DRX inactivity timer value, and the NAS back-off timer value for the MTC UE 111. Used to determine one.
- the eNodeB 112 applies RRC inactivity individually applied to the MTC UE 111.
- timer and DRX inactivity timer may be shortened.
- the eNodeB 112 may shorten the RRC inactivity timer and the DRX inactivity timer for the MTC UE 111 as the communication interval of the MTC UE 111 increases. By shortening the RRC inactivity timer, it is possible to reduce the load on the eNodeB 112 required for managing the RRC connection.
- UE111 can be reduced by shortening RRC
- the eNodeB 112 may lengthen the RRC inactivity timer and the DRX inactivity timer as the communication interval of the MTC UE 111 becomes shorter (or as the communication frequency becomes higher). This reduces the signaling load on the eNodeB 112 and MME 121 caused by the MTC UE 111 frequently repeating state transitions between the idle state (RRC_IDLE state and ECM-IDLE state) and the connected state (RRC_CONNECTED state and ECM-CONNECTED state). it can.
- the MME 121 is individually applied to the MTC UE 111.
- the NAS back-off timer may be lengthened.
- the communication interval of MTC UE 111 is long, it can be estimated that the MTC UE 111 has a large delay tolerance. Therefore, by extending the NAS back-off timer of MTCMTUE 111 as described above, the NAS back-off time can be adapted to the delay tolerance of MTC UE 111, and further contribute to avoiding congestion.
- the device information indicates the communication characteristics of MTC UE 111.
- the communication characteristics of MTC UE 111 may indicate the length of the communication interval of MTC UE 111, the magnitude of the communication frequency, or the delay tolerance level.
- the M2M service is the Intelligent Transport Systems (ITS) service.
- the communication characteristics indicated by the device information may indicate whether the vehicle is running or whether the vehicle engine is started. . From the fact that the vehicle is traveling, it can be inferred that the communication frequency of MTC UE 111 is higher than in the case where the vehicle is not. Moreover, it can be presumed that the communication frequency of MTC UE 111 is higher than that in the case where the engine of the vehicle is started. Further, the communication characteristic indicated by the device information may indicate whether or not an auxiliary function related to the ITS service installed in the navigation system mounted on the vehicle is ON. Since the auxiliary function regarding the ITS service is ON, it can be estimated that the communication frequency of the MTC UE 111 is higher than that in the case where the auxiliary function is not.
- M2M service is tracking cargo in logistics services. If the MTC UE 111 is a device attached to a cargo, the communication characteristics indicated by the device information may indicate whether the cargo is being transported or placed at a distribution center. From the fact that the cargo is being transported, it can be estimated that the communication frequency of the MTC-UE 111 is greater than when the cargo is placed at the distribution center.
- a further example of M2M service is smart metering.
- the communication characteristics indicated by the device information may indicate whether the metering device or sensor is in normal operation or abnormal operation. From the fact that the metering device or sensor is in an abnormal operation, it can be estimated that the communication frequency of MTC UE 111 is higher than that in the normal operation.
- the abnormal operation of the metering device is, for example, an operation when a failure is detected or when the power supply is cut off by operating the breaker.
- the abnormal operation of the sensor is, for example, an operation when the precipitation amount exceeds the threshold and the tide level exceeds the threshold.
- step S ⁇ b> 101 the SCS 131 transmits a UE CHARACTERISTICS NOTIFY message to the MTC-IWF 123.
- the SCS 131 may transmit a UE-CHARACTERISTICS-NOTIFY message in response to detecting a change in UE characteristics (specifically, communication characteristics) of the MTC-UE 111.
- the UE-CHARACTERISTICS-NOTIFY message indicates the external identifier (External ID) of the MTC UE 111 and the communication information of the MTC UE 111.
- the external identifier is used for identifying the MTC UE 111 in the M2M service platform 130 or the MTC application server 132.
- the external identifier may be, for example, Mobile Subscriber Integrated Services Digital Network Number (MSISDN).
- MSISDN Mobile Subscriber Integrated Services Digital Network Number
- UE111 shows the communication characteristic (for example, communication interval, communication frequency, or delay tolerance level) of MTC
- the MTC-IWF 123 transfers the UE-CHARACTERISTICS-NOTIFY message to the HSS / HLR 122.
- the HSS / HLR 122 receives the UE CHARACTERISTICS NOTIFY message and searches for the internal identifier (Internal ID) of the MTC UE 111 based on the external identifier of the MTC UE 111.
- the internal identifier may be, for example, International Mobile Subscriber Identity (IMSI).
- step S104 the HSS / HLR 122 transmits a UE-CHARACTERISTICS-NOTIFY message to the MME 121 that is managing the mobility of the MTC-UE 111.
- the UE CHARACTERISTICS NOTIFY message transmitted in step S104 includes an internal identifier (e.g., IMSI) to specify MTC UE111.
- the MME 121 updates the core network assistant information (CN assistant information) regarding the MTC UE 111.
- the MME 121 may hold communication information indicating the communication characteristics of the MTC UE 111 as part of the MM context of the MTC UE 111.
- the MME 121 transmits a response message (ACK message) to the HSS / HLR 122.
- the HSS / HLR 122 returns a response message (ACK message) to the MTC-IWF 123.
- the MTC-IWF 123 returns a response message (ACK message) to the SCS 131.
- the MME 121 transmits core network assistant information related to the MTC UE 111 to the eNodeB 112.
- an S1AP message transmitted on the S1-MME interface between the MME 121 and the eNodeB 112 can be used.
- the MME 121 may transmit the core network assistant information to the eNodeB 112 using the S1AP: “INITIAL” CONTEXT “SETUP” REQUEST message during the Service “Request” procedure started by the MTC “UE 111”.
- step S110 the eNodeB 112 sets the RRC inactivity timer or DRX inactivity timer applied to the MTC UE 111 or both based on the core network assistant information including the communication information of the MTC UE 111 notified from the MME 121. And eNodeB112 controls the radio
- FIG. 3 shows another specific example of the procedure for updating the values of RRC inactivity timer and DRX inactivity timer.
- the MME 121 receives a UE CHARACTERISTICS NOTIFY message indicating the communication characteristics of the MTC UE 111 from the HSS / HLR 122 via the S6a reference point.
- the MME 121 receives the UE CHARACTERISTICS ⁇ NOTIFY message indicating the communication characteristics of the MTC UE 111 from the MTC-IWF 123 via the T5b reference point.
- step S201 in FIG. 3 The process performed in step S201 in FIG. 3 is the same as the process performed in step S101 in FIG.
- step S202 the MTC-IWF 123 inquires of the HSS / HLR 122 for an internal identifier corresponding to the external identifier (e.g., MSISDN) of the MTC UE 111 in order to obtain the internal identifier (e.g., IMSI) of the MTC UE 111.
- the MTC-IWF 123 may request the subscriber information corresponding to the external identifier of the MTC-UE 111 from the HSS / HLR 122.
- step S203 the HSS / HLR 122 searches for the internal identifier of the MTC UE 111 based on the external identifier of the MTC UE 111. Then, the HSS / HLR 122 transmits to the MTC-IWF 123 a response message indicating the internal identifier (e.g., IMSI) of the MTC UE 111 and the identifier of the MME (MME Identity) performing the mobility management of the MTC UE 111.
- MME Identity may be, for example, Globally Unique Unique MME Identity (GUMMEI), MME IP address, or both.
- GUMMEI Globally Unique Unique MME Identity
- MME IP address or both.
- step S202 and S203 may be abbreviate
- the MTC-IWF 123 transmits a UE-CHARACTERISTICS-NOTIFY message to the MME 121 that is managing the mobility of the MTC-UE 111.
- the UE CHARACTERISTICS NOTIFY message transmitted in step S204 includes an internal identifier (e.g., IMSI) to specify MTC UE111.
- step S205 The process performed in step S205 is the same as the process performed in step S105 of FIG.
- step S206 the MME 121 returns a response message (ACK message) to the MTC-IWF 123.
- step S207 the MTC-IWF 123 returns a response message (ACK message) to the SCS 131.
- the processing performed in steps S208 and S209 is the same as the processing performed in steps S109 and S110 in FIG.
- FIG. 4 shows a specific example of the procedure for updating the NAS back-off timer value.
- the processing performed in steps S301 to S304 is the same as the processing performed in steps S101 to S104 in FIG.
- step S305 the MME 121 updates the value of the NAS back-off timer applied individually to the MTC UE 111 stored in association with the internal identifier (e.g., IMSI) of the MTC UE 111.
- the MME 121 may hold the value of the NAS back-off timer as part of the MM context of the MTC UE 111.
- the MME 121 rejects the NAS request from the MTC UE 111, the MME 121 notifies the MTC UE 111 of the updated NAS back-off timer value.
- the processing performed in steps S306 to S308 is the same as the processing performed in steps S106 to S108 in FIG.
- FIG. 5 shows another specific example of the procedure for updating the value of the NAS back-off timer.
- the MME 121 receives a UE CHARACTERISTICS NOTIFY message indicating the communication characteristics of the MTC UE 111 from the MTC-IWF 123 via the T5b reference point.
- the processing performed in steps S401 to S404 is the same as the processing performed in steps S201 to S204 in FIG.
- the process performed in step S405 is the same as the process performed in step S305 in FIG.
- the processing performed in steps S406 and S407 is the same as the processing performed in steps S206 and S207 in FIG.
- the MTC-IWF 123 in the EPC 120 transmits a message (eg, UE CHARACTERISTICS NOTIFY message) indicating the communication characteristics of the MTC UE 111 to the entity (eg, SCS 131). Then, the eNodeB 112 in the E-UTRAN 110 determines the value of the RRC inactivity timer and / or the value of the DRX inactivity timer individually applied to the MTC UE 111 based on the communication characteristics of the MTC UE 111 notified from the M2M service platform 130. decide.
- a message eg, UE CHARACTERISTICS NOTIFY message
- the MME 121 in the EPC 120 determines the value of the NAS back-off timer individually applied to the MTC UE 111 based on the communication characteristics of the MTC UE 111 notified from the M2M service platform 130. Therefore, the PLMN including the E-UTRAN 110 and the EPC 120 according to the present embodiment can manage the connection of the MTC device (ie, MTC UE111) in the PLMN in the M2M service platform 130 or the MTC application server 132 (ie, This can be done using the communication characteristics of MTC UE 111).
- FIG. 6 shows a configuration example of the MME 121.
- the MME 121 includes a network interface 1210, a processor 1211, and a memory 1212.
- the network interface 1210 is used to communicate with other network nodes (e.g., eNodeB 112, HSS / HLR 122, MTC-IWF 123, and S-GW 124).
- the network interface 1210 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.
- NIC network interface card
- the processor 1211 executes communication control (e.g., mobility management and bearer management) by reading and executing software (computer program) from the memory 1212.
- the processor 1211 may be, for example, a microprocessor, a Micro Processing Unit (MPU), or a Central Processing Unit (CPU).
- the processor 1211 may include a plurality of processors.
- the memory 1212 is configured by a combination of a volatile memory and a nonvolatile memory.
- the volatile memory is, for example, Static Random Access Memory (SRAM), Dynamic RAM (DRAM), or a combination thereof.
- the nonvolatile memory is, for example, a mask Read Only Memory (MROM), Programmable ROM (PROM), flash memory, hard disk drive, or a combination thereof.
- the memory 1212 may include storage that is physically separated from the processor 1211. In this case, the processor 1211 may access the memory 1212 via the network interface 1210 or another I / O interface not shown.
- the memory 1212 includes an S1-MME module 1213, an S6a module 1214, an S10 module 1215, an S11 module 1216, a NAS module 1217, and an EPS Mobility Management (EMM) and EPS Session Management (ESM) module 1218.
- EMM EPS Mobility Management
- ESM EPS Session Management
- the EMM and ESM module 1218 includes the RRC inactivity timer value, the DRX inactivity timer value, and the NAS backoff timer value based on the communication characteristics of the MTC UE 111 informed from the M2M service platform described in the above embodiment. It includes instructions and data for performing the update procedure.
- the processor 1211 reads the EMMEM and ESM module 1218 from the memory 1212 and executes them to update the RRC inactivity timer value, the DRX inactivity timer value, and the NAS back-off timer value described in the above embodiment.
- the operation of the MME 121 can be performed.
- FIG. 7 shows a configuration example of the eNodeB 112.
- the eNodeB 112 includes a wireless transceiver 1120, a network interface 1121, a processor 1122, and a memory 1123.
- the radio transceiver 1120 is configured to communicate with a plurality of UEs including the MTC UE 111.
- the network interface 1121 is used to communicate with other eNodeBs within the E-UTRAN 110 and nodes (such as the MME 121 and the S-GW 124) within the EPC 120.
- the processor 1122 reads out and executes software (computer program) from the memory 1123, thereby performing communication control including RRC and Radio Resource Management (RRM) and the operation of the eNodeB 112 described in the above-described embodiment.
- the processor 1122 may be, for example, a microprocessor, MPU, or CPU.
- the processor 1122 may include a plurality of processors.
- the memory 1123 is configured by a combination of a volatile memory and a nonvolatile memory.
- the volatile memory is, for example, SRAM or DRAM or a combination thereof.
- the non-volatile memory is, for example, an MROM, PROM, flash memory, hard disk drive, or a combination thereof.
- the memory 1123 may include a storage disposed away from the processor 1122. In this case, the processor 1122 may access the memory 1123 via the network interface 1121 or another I / O interface not shown.
- the memory 1123 is used to store a software module group including the RRC module 1124, the RRM module 1125, the X2 module 1126, and the S1-MME module 1127.
- the processor 1122 reads out the RRC module 1124 from the memory 1123 and executes it, thereby performing the operation of the eNodeB 112 related to the update procedure of the RRC inactivity timer value and the DRX inactivity timer value described in the above embodiment.
- FIG. 8 shows a configuration example of the SCS 131.
- the SCS 131 includes a network interface 1310, a processor 1311, and a memory 1312.
- the network interface 1310 is used to communicate with other network nodes (e.g., MTC-IWF 123 and MTC application server 132).
- the network interface 1310 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.
- NIC network interface card
- the processor 1311 reads out and executes software (computer program) from the memory 1312 to execute communication control for the MTC device (e.g., device trigger, acquisition of communication characteristics of the MTC device).
- the processor 1311 may be, for example, a microprocessor, MPU, or CPU.
- the processor 1311 may include a plurality of processors.
- the memory 1312 is configured by a combination of a volatile memory and a nonvolatile memory.
- the volatile memory is, for example, SRAM or DRAM or a combination thereof.
- the non-volatile memory is, for example, an MROM, PROM, flash memory, hard disk drive, or a combination thereof.
- the memory 1312 may include storage that is physically located away from the processor 1311. In this case, the processor 1311 may access the memory 1312 via the network interface 1310 or another I / O interface not shown.
- the memory 1312 is used to store a software module group including a Tsp module 1313, an SGi module 1314, and a UE characteristic management module 1315.
- the UE characteristic management module 1315 executes the procedure described in the above embodiment to inform the EPC 120 (ie, MTC-IWF123) of the communication characteristics of the MTC UE 111 grasped by the M2M service platform 130 or the MTC application server 132. Instruction group and data.
- the processor 1311 reads the UE characteristic management module 1315 from the memory 1312 and executes it to update the RRC inactivity timer value, the DRX inactivity timer value, and the NAS back-off timer value described in the above embodiment.
- the operation of the SCS 131 can be performed.
- each of the processors included in the MME 121, eNodeB 112, and SCS 131 is a command for causing a computer to execute the algorithm described using the sequence diagram or the like. Run one or more programs that contain groups.
- Non-transitory computer readable media include various types of tangible storage media (tangible storage medium). Examples of non-transitory computer-readable media are magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical discs), Compact Disc Read Only Memory (CD-ROM), CD-ROM R, CD-R / W, semiconductor memory (for example, mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)).
- the program may also be supplied to the computer by various types of temporary computer-readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves.
- the temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
- the architecture shown in FIG. 1 is only an example of an architecture for MTC in 3GPP.
- functions and entities located in the M2M service platform 130 (MTC service platform, exposure layer) and their names may change in future releases or versions.
- the SCS 131 described in the present embodiment may be called an API Gateway Function (API-GWF).
- API-GWF API Gateway Function
- the function of SCS131 may be divided
- the technical idea described in the above embodiment can be applied to the architecture for these modified MTCs.
- UMTS Universal Mobile Telecommunications System
- HRPD High Rate Packet Data
- GSM Global System for Mobile Communications
- GPRS General packet radio service
- Evolved Universal Terrestrial Radio Access Network 111 User Equipment (UE) 112 eNodeB 120 Evolved Packet Core (EPC) 121 Mobility Management Entity (MME) 122 Home Subscriber Server (HSS) 123 Machine Type Communication Inter Working Function (MTC-IWF) 124 Serving Gateway (S-GW) 125 Packet Data Network Gateway (P-GW) 130 Machine-to-Machine (M2M) Service Platform 131 Service Capability Server (SCS) 132 MTC Application Server (AS)
- EPC Evolved Packet Core
- MME Mobility Management Entity
- HSS Home Subscriber Server
- MTC-IWF Machine Type Communication Inter Working Function
- S-GW Serving Gateway
- P-GW Packet Data Network Gateway
- M2M Machine-to-Machine
- SCS Service Capability Server
- AS MTC Application Server
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
図1に示されたアーキテクチャは、3GPPにおけるMTCのためのアーキテクチャの一例に過ぎない。例えば、M2Mサービスプラットフォーム130(MTCサービスプラットフォーム、エクスポージャーレイヤ)内に配置されるファンクション及びエンティティ並びにこれらの名称は、将来のリリース又はバージョンにおいて変更されるかもしれない。例えば、本実施形態において説明されたSCS131は、API Gateway Function(API-GWF)と呼ばれるかもしれない。あるいは、SCS131の機能は、SCSとAPI-GWFに分割して配置されるかもしれない。上述の実施形態で説明された技術思想は、これらの変形されたMTCのためのアーキテクチャにも適用することができる。
111 User Equipment (UE)
112 eNodeB
120 Evolved Packet Core (EPC)
121 Mobility Management Entity (MME)
122 Home Subscriber Server (HSS)
123 Machine Type Communication Inter Working Function (MTC-IWF)
124 Serving Gateway (S-GW)
125 Packet Data Network Gateway (P-GW)
130 Machine-to-Machine (M2M) サービスプラットフォーム
131 Service Capability Server (SCS)
132 MTC Application Server (AS)
Claims (21)
- コアネットワーク内に配置されるモビリティ管理エンティティによって行われる方法であって、
Machine Type Communication(MTC)デバイスの通信特性を、前記コアネットワーク及び無線アクセスネットワークを含む移動通信ネットワークによって提供されるサービスを利用できるようにするためのアプリケーション・プログラミング・インタフェース(API)をMTCアプリケーションサーバに対して提供するMTCサービスプラットフォームから、前記コアネットワーク内のネットワーク・エンティティを介して受信すること、及び
(a)コネクテッド状態の前記MTCデバイスがアイドル状態に遷移するタイミングを制御するために前記無線アクセスネットワークにおいて使用される第1のインアクティビティ・タイマの値、(b)前記MTCデバイスが前記コネクテッド状態において間欠受信を開始するタイミングを規定するために前記無線アクセスネットワークにおいて使用される第2のインアクティビティ・タイマの値、及び(c)アップリンクNon-Access Stratum(NAS)メッセージの送信抑止のために前記MTCデバイスに配置されるNASバックオフタイマの値、のうち少なくとも1つを前記通信特性に基づいて更新するよう制御すること、
を備える、
方法。 - 前記制御することは、前記第1及び第2のインアクティビティ・タイマのうち少なくとも一方を更新するために、前記通信特性を前記無線アクセスネットワーク内の無線ネットワーク制御エンティティに知らせることを含む、請求項1に記載の方法。
- 前記制御することは、前記モビリティ管理エンティティにおいて管理されている前記NASバックオフタイマの値を更新することを含む、請求項1に記載の方法。
- 前記通信特性は、前記MTCデバイスの通信間隔、通信頻度、又は遅延許容性レベルを示す、請求項1に記載の方法。
- 前記MTCデバイスは、車両に取り付けられるデバイスであり、
前記通信特性は、前記車両が走行中であるか否か、前記車両のエンジンが始動されているか、又は前記車両に搭載されたナビゲーションシステムの補助機能がONであるか否かを示す、
請求項1に記載の方法。 - 前記MTCデバイスは、貨物に取り付けられるデバイスであり、
前記通信特性は、前記貨物が輸送中であるか否かを示す、
請求項1に記載の方法。 - 前記MTCデバイスは、メータリング装置またはセンサに結合されたデバイスであり、
前記通信特性は、前記メータリング装置または前記センサが通常運用であるか異常運用であるかを示す、
請求項1に記載の方法。 - 無線アクセスネットワーク内に配置される無線ネットワーク制御エンティティによって行われる方法であって、
Machine Type Communication(MTC)デバイスの通信特性を、コアネットワーク及び前記無線アクセスネットワークを含む移動通信ネットワークによって提供されるサービスを利用できるようにするためのアプリケーション・プログラミング・インタフェース(API)をMTCアプリケーションサーバに対して提供するMTCサービスプラットフォームから、前記コアネットワーク内のモビリティ管理エンティティを介して受信すること、及び
(a)コネクテッド状態の前記MTCデバイスがアイドル状態に遷移するタイミングを制御するために前記無線アクセスネットワークにおいて使用される第1のインアクティビティ・タイマの値、及び(b)前記MTCデバイスが前記コネクテッド状態において間欠受信を開始するタイミングを規定するために前記無線アクセスネットワークにおいて使用される第2のインアクティビティ・タイマの値、のうち少なくとも1つを前記通信特性に基づいて決定すること、
を備える、
方法。 - 前記通信特性は、前記MTCデバイスの通信間隔、通信頻度、又は遅延許容性レベルを示す、請求項8に記載の方法。
- 前記無線ネットワーク制御エンティティは、基地局又はRadio Network Controller(RNC)である、請求項8又は9に記載の方法。
- コアネットワーク内に配置されるモビリティ管理エンティティであって、
メモリと、
前記メモリに結合され、制御方法を行うよう構成されたプロセッサと、
を備え、
前記制御方法は、
Machine Type Communication(MTC)デバイスの通信特性を、前記コアネットワーク及び無線アクセスネットワークを含む移動通信ネットワークによって提供されるサービスを利用できるようにするためのアプリケーション・プログラミング・インタフェース(API)をMTCアプリケーションサーバに対して提供するMTCサービスプラットフォームから、前記コアネットワーク内のネットワーク・エンティティを介して受信すること、及び
(a)コネクテッド状態の前記MTCデバイスがアイドル状態に遷移するタイミングを制御するために前記無線アクセスネットワークにおいて使用される第1のインアクティビティ・タイマの値、(b)前記MTCデバイスが前記コネクテッド状態において間欠受信を開始するタイミングを規定するために前記無線アクセスネットワークにおいて使用される第2のインアクティビティ・タイマの値、及び(c)アップリンクNon-Access Stratum(NAS)メッセージの送信抑止のために前記MTCデバイスに配置されるNASバックオフタイマの値、のうち少なくとも1つを前記通信特性に基づいて更新するよう制御すること、
を備える、
モビリティ管理エンティティ。 - 前記制御することは、前記第1及び第2のインアクティビティ・タイマのうち少なくとも一方を更新するために、前記通信特性を前記無線アクセスネットワーク内の無線ネットワーク制御エンティティに知らせることを含む、請求項11に記載のモビリティ管理エンティティ。
- 前記制御することは、前記モビリティ管理エンティティにおいて管理されている前記NASバックオフタイマの値を更新することを含む、請求項11に記載のモビリティ管理エンティティ。
- 無線アクセスネットワーク内に配置される無線ネットワーク制御エンティティであって、
メモリと、
前記メモリに結合され、制御方法を行うよう構成されたプロセッサと、
を備え、
前記制御方法は、
Machine Type Communication(MTC)デバイスの通信特性を、コアネットワーク及び前記無線アクセスネットワークを含む移動通信ネットワークによって提供されるサービスを利用できるようにするためのアプリケーション・プログラミング・インタフェース(API)をMTCアプリケーションサーバに対して提供するMTCサービスプラットフォームから、前記コアネットワーク内のモビリティ管理エンティティを介して受信すること、及び
(a)コネクテッド状態の前記MTCデバイスがアイドル状態に遷移するタイミングを制御するために前記無線アクセスネットワークにおいて使用される第1のインアクティビティ・タイマの値、及び(b)前記MTCデバイスが前記コネクテッド状態において間欠受信を開始するタイミングを規定するために前記無線アクセスネットワークにおいて使用される第2のインアクティビティ・タイマの値、のうち少なくとも1つを前記通信特性に基づいて更新するよう制御すること、
を備える、
無線ネットワーク制御エンティティ。 - 前記通信特性は、前記MTCデバイスの通信間隔、通信頻度、又は遅延許容性レベルを示す、請求項14に記載の無線ネットワーク制御エンティティ。
- 請求項1~7のいずれか1項に記載の方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体。
- 請求項8~10のいずれか1項に記載の方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体。
- コアネットワーク及び無線アクセスネットワークを含む移動通信ネットワークを介してMachine Type Communication(MTC)デバイスと通信するMTCアプリケーションサーバに対して前記移動通信ネットワークによって提供されるサービスを利用できるようにするためのアプリケーション・プログラミング・インタフェース(API)を提供するサービス能力エンティティによって行われる方法であって、
前記MTCデバイスの通信特性を示す第1のメッセージを前記コアネットワーク内のネットワーク・エンティティに送信することを備え、
前記第1のメッセージは、(a)コネクテッド状態の前記MTCデバイスがアイドル状態に遷移するタイミングを制御するために前記無線アクセスネットワークにおいて使用される第1のインアクティビティ・タイマの値、(b)前記MTCデバイスが前記コネクテッド状態において間欠受信を開始するタイミングを規定するために前記無線アクセスネットワークにおいて使用される第2のインアクティビティ・タイマの値、及び(c)アップリンクNon-Access Stratum(NAS)メッセージの送信抑止のために前記MTCデバイスに配置されるNASバックオフタイマの値、のうち少なくとも1つの更新を引き起こす、
方法。 - 前記通信特性は、前記MTCデバイスの通信間隔、通信頻度、又は遅延許容性レベルを示す、請求項18に記載の方法。
- コアネットワーク及び無線アクセスネットワークを含む移動通信ネットワークを介してMachine Type Communication(MTC)デバイスと通信するMTCアプリケーションサーバに対して前記移動通信ネットワークによって提供されるサービスを利用できるようにするためのアプリケーション・プログラミング・インタフェース(API)を提供するサービス能力エンティティであって、
メモリと、
前記メモリに結合され、制御方法を実行するよう構成されたプロセッサと、
を備え、
前記制御方法は、前記MTCデバイスの通信特性を示す第1のメッセージを前記コアネットワーク内のネットワーク・エンティティに送信することを備え、
前記第1のメッセージは、(a)コネクテッド状態の前記MTCデバイスがアイドル状態に遷移するタイミングを制御するために前記無線アクセスネットワークにおいて使用される第1のインアクティビティ・タイマの値、(b)前記MTCデバイスが前記コネクテッド状態において間欠受信を開始するタイミングを規定するために前記無線アクセスネットワークにおいて使用される第2のインアクティビティ・タイマの値、及び(c)アップリンクNon-Access Stratum(NAS)メッセージの送信抑止のために前記MTCデバイスに配置されるNASバックオフタイマの値、のうち少なくとも1つの更新を引き起こす、
MTCサービス・エンティティ。 - コアネットワーク及び無線アクセスネットワークを含む移動通信ネットワークを介してMachine Type Communication(MTC)デバイスと通信するMTアプリケーションサーバに対して前記移動通信ネットワークによって提供されるサービスを利用できるようにするためのアプリケーション・プログラミング・インタフェース(API)を提供するサービス能力エンティティによって行われる制御方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、
前記制御方法は、前記MTCデバイスの通信特性を示す第1のメッセージを前記コアネットワーク内のネットワーク・エンティティに送信することを備え、
前記第1のメッセージは、(a)コネクテッド状態の前記MTCデバイスがアイドル状態に遷移するタイミングを制御するために前記無線アクセスネットワークにおいて使用される第1のインアクティビティ・タイマの値、(b)前記MTCデバイスが前記コネクテッド状態において間欠受信を開始するタイミングを規定するために前記無線アクセスネットワークにおいて使用される第2のインアクティビティ・タイマの値、及び(c)アップリンクNon-Access Stratum(NAS)メッセージの送信抑止のために前記MTCデバイスに配置されるNASバックオフタイマの値、のうち少なくとも1つの更新を引き起こす、
非一時的なコンピュータ可読媒体。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016534086A JP6515929B2 (ja) | 2014-07-14 | 2015-05-13 | コネクション管理のための方法および装置 |
US15/325,910 US20170196028A1 (en) | 2014-07-14 | 2015-05-13 | Method and apparatus for connection management |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014144080 | 2014-07-14 | ||
JP2014-144080 | 2014-07-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016009578A1 true WO2016009578A1 (ja) | 2016-01-21 |
Family
ID=55078093
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/002418 WO2016009578A1 (ja) | 2014-07-14 | 2015-05-13 | コネクション管理のための方法および装置 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20170196028A1 (ja) |
JP (1) | JP6515929B2 (ja) |
WO (1) | WO2016009578A1 (ja) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110290158A (zh) * | 2018-03-19 | 2019-09-27 | 比亚迪股份有限公司 | 列车通信网络节点的更新方法及系统 |
CN112738760A (zh) * | 2019-10-28 | 2021-04-30 | 通用汽车环球科技运作有限责任公司 | 用户控制的车辆连通可用性 |
CN115499892A (zh) * | 2017-03-15 | 2022-12-20 | 诺基亚通信公司 | 用于网络重新附接的退避定时器 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10469600B2 (en) * | 2017-11-14 | 2019-11-05 | Dell Products, L.P. | Local Proxy for service discovery |
WO2019141212A1 (en) * | 2018-01-17 | 2019-07-25 | Mediatek Singapore Pte. Ltd. | Application of nas-level congestion control timer values at intersystem change |
CN111200841B (zh) * | 2018-11-16 | 2021-06-04 | 电信科学技术研究院有限公司 | 消息发送及其控制方法及装置 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014013661A1 (ja) * | 2012-07-20 | 2014-01-23 | 日本電気株式会社 | コアネットワークノード、無線端末、輻輳制御のための方法、及び非一時的なコンピュータ可読媒体 |
WO2014054237A1 (ja) * | 2012-10-04 | 2014-04-10 | 日本電気株式会社 | 無線アクセスネットワーク装置、コアネットワーク装置、移動端末、並びにこれらの方法及びコンピュータ可読媒体 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080122691A1 (en) * | 2006-11-27 | 2008-05-29 | Carani Sherry L | Tracking system and method with multiple time zone selector, dynamic screens and multiple screen presentations |
US9510285B2 (en) * | 2010-07-23 | 2016-11-29 | Qualcomm Incorporated | User device dormancy |
US20120033613A1 (en) * | 2010-08-04 | 2012-02-09 | National Taiwan University | Enhanced rach design for machine-type communications |
BR112014022171B1 (pt) * | 2012-03-23 | 2022-09-20 | Nec Corporation | Servidor de assinante doméstico, servidor de monitoramento, método executado por um servidor de assinante doméstico |
WO2014085622A1 (en) * | 2012-11-30 | 2014-06-05 | Interdigital Patent Holdings, Inc. | Method and gateway to handle inactivity timer expiry with a converged gateway |
-
2015
- 2015-05-13 WO PCT/JP2015/002418 patent/WO2016009578A1/ja active Application Filing
- 2015-05-13 JP JP2016534086A patent/JP6515929B2/ja active Active
- 2015-05-13 US US15/325,910 patent/US20170196028A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014013661A1 (ja) * | 2012-07-20 | 2014-01-23 | 日本電気株式会社 | コアネットワークノード、無線端末、輻輳制御のための方法、及び非一時的なコンピュータ可読媒体 |
WO2014054237A1 (ja) * | 2012-10-04 | 2014-04-10 | 日本電気株式会社 | 無線アクセスネットワーク装置、コアネットワーク装置、移動端末、並びにこれらの方法及びコンピュータ可読媒体 |
Non-Patent Citations (2)
Title |
---|
"InterDigital Communications, Optimisation of CN assisted eNB parameter tuning for small data transfer solution", SA WG2 MEETING #S2-97, 21 May 2013 (2013-05-21), pages 2 - 131900, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/ tsg_sa/wg2_arch/TSGS2_97_Busan/Docs/S2-131900> * |
HTC: "Overload handing by UE reachability interrogation from SCS", SA WG2 MEETING #S2-97, 21 May 2013 (2013-05-21), pages 2 - 131786, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/ tsg_sa/wg2_arch/TSGS2_97_Busan/Docs/S2-131786. zip> * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115499892A (zh) * | 2017-03-15 | 2022-12-20 | 诺基亚通信公司 | 用于网络重新附接的退避定时器 |
CN110290158A (zh) * | 2018-03-19 | 2019-09-27 | 比亚迪股份有限公司 | 列车通信网络节点的更新方法及系统 |
CN110290158B (zh) * | 2018-03-19 | 2021-09-03 | 比亚迪股份有限公司 | 列车通信网络节点的更新方法及系统 |
CN112738760A (zh) * | 2019-10-28 | 2021-04-30 | 通用汽车环球科技运作有限责任公司 | 用户控制的车辆连通可用性 |
CN112738760B (zh) * | 2019-10-28 | 2024-05-24 | 通用汽车环球科技运作有限责任公司 | 用户控制的车辆连通可用性 |
Also Published As
Publication number | Publication date |
---|---|
JP6515929B2 (ja) | 2019-05-22 |
US20170196028A1 (en) | 2017-07-06 |
JPWO2016009578A1 (ja) | 2017-05-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016009580A1 (ja) | 通信管理のための方法および装置 | |
US10887940B2 (en) | Policy determination system, policy determination method, and non-transitory computer-readable medium | |
US11405974B2 (en) | Communication system | |
US10484864B2 (en) | Subscriber server, monitoring server, mobile terminal, methods related thereto, and computer readable medium | |
WO2016009578A1 (ja) | コネクション管理のための方法および装置 | |
US9661571B2 (en) | Method of determining expiration period of timer, network node, and non-transitory computer readable medium | |
US8755766B2 (en) | Handling reachability of mobile device when serving core network node changes | |
US8428589B2 (en) | Method for reducing signalling | |
US11412565B2 (en) | Communication system | |
US20150358837A1 (en) | Mobile communication system, service platform, network parameter control method, and computer readable medium | |
EP2957135B1 (en) | Method and network node for setting a mobile communication terminal in an idle mode | |
WO2016009579A1 (ja) | モビリティ管理のための方法および装置 | |
WO2014125776A1 (ja) | 通信システム、通信装置、ネットワークパラメータ制御方法及び非一時的なコンピュータ可読媒体 | |
US20160029431A1 (en) | Method of determining expiration period of timer, network node, base station, and non-transitory computer readable medium | |
CN113170411B (zh) | 无线通信方法、装置及计算机可读介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15821261 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016534086 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15325910 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15821261 Country of ref document: EP Kind code of ref document: A1 |