JP6733736B2 - SCEF entity and data processing method - Google Patents

Description

The present invention relates to a SCEF (Service Capability Exposure Function) entity, a communication terminal, a data processing method, a data receiving method, and a program, for example, a SCEF entity that processes Non-IP data, a communication terminal, a data processing method, a data receiving method, And the program.

2. Description of the Related Art In recent years, mobile communication technology related to IoT (Internet of Things) that allows various devices (things) to have a mobile communication function to connect to the Internet and communicate between devices has been developed. One of the challenges in providing devices with mobile communication functions is the reduction of power consumption. It is expected that the sensor devices will operate without maintenance for a long period of several years. It is desirable to reduce communication power consumption in order to provide such a device with a mobile communication function.

The 3rd Generation Partnership Project (3GPP), which defines the standard specifications for mobile communication, defines Non-IP data delivery that performs data communication without using the IP protocol stack, as one of the technologies for reducing the power consumption of communication. There is.

Section 5.13.3 of Non-Patent Document 1 discloses a configuration example of performing non-IP data delivery of downlink (from the network to the terminal) in an EPC (Evolved Packet Core) network, and a procedure in the configuration example. ..

In this configuration example, the UE (User Equipment) that receives the Non-IP data, the SCS (Services Capability Server) or AS (Application Server) that is the transmission source of the Non-IP data, and the Non-IP data is accepted and authorized. Non-IP data is transmitted to the UE using SCEF (Service Capability Exposure Function) that performs communication amount control and rate control (load control) and a C (Control)-Plane message (for example, NAS (Non Access Stratum) message). And an exchange MME (Mobility Management Entity) to be transmitted to.

3GPP TS 23.682 V14.1.0 (2016-09) Section 5.13.3

In mobile communication, downlink (from the network to the terminal) communication may be temporarily unreachable (UE is unreachable) due to the power save mode status of the UE, the radio wave status, and the like. In Section 5.13.3 of Non-Patent Document 1, in the procedure of performing downlink Non-IP data delivery (from the network to the terminal), if the downlink communication is unreachable to the UE, the UE is reachable. After that, Non-IP data delivery is performed.

The MME receives the Non-IP data delivery transmission request (NIDD Submit Request) from the SCEF. When the MME detects that the UE is unreachable, it returns a response (NIDD Submit Response) to the non-IP data delivery transmission request including a Cause indicating that the Non-IP data was not delivered to the UE. To do. When the MME detects that the UE is reachable (UE is reachable), the Cause set in the Non-IP data delivery transmission request is notified to the SCEF by the MME (NIDD Submit Indication). Indicates that

The SCEF receiving the above response (NIDD Submit Response) buffers the Non-IP data until the NIDD Submit Indication is transmitted from the MME. Finally, the SCEF retransmits the Non-IP data delivery transmission request upon receiving the NIDD Submit Indication from the MME.

However, if there are two or more Non-IP data delivery transmission requests from the SCS or AS to the corresponding UE while the UE is unreachable, the following problem occurs.

Due to the UE being unreachable, the SCEF receives a Non-IP data delivery transmission request for the second Non-IP data from the SCS or AS while the SCEF is buffering the first Non-IP data. Sometimes. In this case, the SCEF sends a Non-IP data delivery send request for the second Non-IP data to the MME. Since the UE is unreachable, the second Non-IP data will not reach the UE and will result in buffering in the SCEF like the first Non-IP data. Therefore, in a situation where the UE is unreachable, the SCEF sending a Non-IP data delivery transmission request for the second Non-IP data has an adverse effect of unnecessarily increasing the communication processing between the SCEF and the MME.

An object of the present invention is to provide a SCEF entity, a communication terminal, a data processing method, a data receiving method, and a program that suppress an increase in processing load related to communication between SCEF and MME in Non-IP data delivery. It is in.

The SCEF entity according to the first aspect of the present invention includes a storage unit that buffers the first Non-IP data that has not been delivered to the communication terminal, and a second Non-IP whose destination is the communication terminal from the server device. When receiving the data, if the first Non-IP data is buffered, it is possible to suppress the transmission of the second Non-IP data to the control device in the mobile network, And a control unit for buffering Non-IP data in the storage unit.

The communication terminal according to the second aspect of the present invention sends a plurality of Non-IP data buffered by the SCEF entity until the own device becomes reachable via the control device when the own device becomes reachable. A communication unit that receives as one message, and a control unit that reads a plurality of Non-IP data included in the one message for each Non-IP data are provided.

A data processing method according to a third aspect of the present invention buffers first Non-IP data that has not been delivered to a communication terminal, and transmits second Non-IP data addressed to the communication terminal from a server device. When the first Non-IP data is buffered when received, the second Non-IP data is suppressed from being transmitted to the control device in the mobile network, and the second Non-IP data is suppressed. It buffers data.

A data communication method according to a fourth aspect of the present invention is configured such that a plurality of Non-IP data buffered by an SCEF entity until the own device becomes reachable is transmitted via the control device when the own device becomes reachable. It is received as one message and a plurality of Non-IP data included in the one message is read for each Non-IP data.

The program according to the fifth aspect of the present invention buffers the first Non-IP data that has not been delivered to the communication terminal, and receives the second Non-IP data addressed to the communication terminal from the server device. At this time, when the first Non-IP data is buffered, transmission of the second Non-IP data to the control device in the mobile network is suppressed, and the second Non-IP data is transmitted. It is what causes the computer to do the buffering.

According to the present invention, it is possible to provide a SCEF entity, a communication terminal, a data processing method, a data receiving method, and a program that suppress an increase in processing load related to communication between SCEF and MME in Non-IP data delivery. ..

1 is a configuration diagram of a communication system according to a first exemplary embodiment. FIG. 3 is a configuration diagram of a communication system according to a second exemplary embodiment. FIG. 9 is a diagram showing a flow of processing when the UE according to the second exemplary embodiment is unreachable. FIG. 9 is a diagram showing a flow of processing when the UE according to the second exemplary embodiment is reachable. FIG. 16 is a diagram showing a flow of a process in which the SCEF according to the third embodiment receives the information about the allowable traffic and the rate. FIG. 9 is a configuration diagram of a UE according to the fourth exemplary embodiment. FIG. 19 is a diagram showing a flow of processing when the UE according to the fourth exemplary embodiment is reachable. FIG. 16 is a diagram showing Non-IP data stored in a buffer according to the fifth exemplary embodiment. FIG. 16 is a diagram showing Non-IP data stored in a buffer according to the fifth exemplary embodiment. It is a block diagram of UE concerning each embodiment. It is a block diagram of SCEF concerning each embodiment.

(Embodiment 1)
Hereinafter, embodiments of the present invention will be described with reference to the drawings. A configuration example of the communication system according to the first exemplary embodiment of the present invention will be described with reference to FIG. The communication system of FIG. 1 includes a SCEF (Service Capability Exposure Function) entity (hereinafter, referred to as SCEF) 10, a control device 20, a server device 30, and a communication terminal 40. The SCEF 10, the control device 20, the server device 30, and the communication terminal 40 may be computer devices that operate when a processor executes a program stored in a memory.

The communication terminal 40 may be a mobile phone terminal, a smartphone terminal, a tablet terminal, or the like. Alternatively, the communication terminal 40 may be an M2M (Mobile to Mobile) terminal, an MTC (Machine Type Communication) terminal, an IoT (Internet of Things) terminal, or the like. The communication terminal 40 communicates with the SCEF entity 10 via the radio access network.

The server device 30 may be, for example, an application server that provides an application service. Alternatively, the server device 30 may be a server device that is arranged between the application server and the SCEF 10 and relays data related to the application service.

The control device 20 is a node device arranged in the mobile network. The control device 20 is a node device that relays or processes control information in the mobile network. The control information may be referred to as, for example, C (Control)-Plane data, C-Plane message, or the like. The control device 20 may be, for example, an MME or SGSN (Serving GPRS (General Packet Radio Service) Support Node) defined in 3GPP.

The SCEF 10 is a node device whose operation is specified in 3GPP. The SCEF 10 is a mobile network defined by 3GPP, and is arranged between a mobile network managed by a mobile communication carrier and a server device managed by a third party other than the mobile communication carrier such as an application server. To be done. The SCEF 10 securely provides the server device 30 with information regarding services that can be supported in the mobile network and the ability to provide the services.

Further, the SCEF 10 delivers or delivers the Non-IP data transmitted from the server device 30 to the communication terminal 40 via the control device 20 in the mobile network. In the following description, the term delivery may be replaced with delivery. Non-IP data is data that does not use the IP protocol stack. Non-IP data refers to data packets used for communication that are unstructured from the perspective of EPS (Evolved Packet System). For example, technologies such as LoRa, SIGFOX, NB-IoT, which are generally called LPWA (Low Power Wide Area), do not establish an IP data bearer in order to reduce device power consumption. In order to address these issues, the 3GPP network defines a mechanism (Non-IP Data Delivery (NIDD)) for exchanging a small amount of data on the C-plane. Non-IP data is transmitted as control information in the mobile network. The Non-IP data may be, for example, data transmitted to an IoT terminal that receives the IoT service.

Subsequently, a configuration example of the SCEF 10 will be described. The SCEF 10 has a storage unit 11 and a control unit 12. The control unit 12 may be software or a module in which processing is executed by the processor executing a program stored in the memory. Alternatively, the control unit 12 may be hardware such as a chip or a circuit. The storage unit 11 may be, for example, a memory.

The storage unit 11 buffers the Non-IP data that has not been delivered to the communication terminal 40. In other words, the storage unit 11 temporarily stores, saves, or stores the Non-IP data before retransmitting the Non-IP data to the communication terminal 40. The case where the Non-IP data is not delivered to the communication terminal 40 may be, for example, the case where the communication terminal 40 is in the power save mode, or the case where the radio wave condition deteriorates and wireless communication cannot be performed. The state where the Non-IP data is not delivered to the communication terminal 40 may be restated as the communication terminal 40 being unreachable. In addition, the state in which the Non-IP data can be delivered to the communication terminal 40 may be restated as the communication terminal 40 being reachable.

When the control unit 12 receives the Non-IP data destined for the communication terminal 40 from the server device 30 and the non-IP data not delivered to the communication terminal 40 is buffered in the storage unit 11, The non-IP data received from the device 30 is suppressed from being transmitted to the control device 20 in the mobile network, and the non-IP data received from the server device 30 is buffered in the storage unit 11. Suppressing transmission of Non-IP data to the control device 20 in the mobile network includes not transmitting Non-IP data to the control device 20 in the mobile network.

The case where the non-IP data that has not been delivered to the communication terminal 40 is buffered in the storage unit 11 is a case where the communication terminal 40 is unreachable. Therefore, even if the new non-IP data addressed to the communication terminal 40 and received by the SCEF 10 from the server device 30 is transmitted to the control device 20, the control device 20 transmits the non-IP data to the communication terminal 40. There is a high possibility that it is not possible or that the Non-IP data cannot be transmitted to the communication terminal 40.

In such a case, the control unit 12 buffers the Non-IP data received from the server device 30 in the storage unit 11 without transmitting it to the control device 20, thereby causing unnecessary traffic in the mobile network. It can be prevented.

(Embodiment 2)
Subsequently, a configuration example of the communication system according to the second exemplary embodiment of the present invention will be described with reference to FIG. The communication system of FIG. 2 includes a SCEF 10, an MME 22, an SGSN 24, a RAN (Radio Access Network) 26, an AS 32, an SCS 34, and a UE 42.

The MME 22 and the SGSN 24 correspond to the control device 20 of FIG. The AS 32 and the SCS 34 correspond to the server device 30 of FIG. The UE 42 corresponds to the communication terminal 40 of FIG. The UE 42 is used as a general term for communication terminals in 3GPP.

The RAN 26 may be, for example, an eNB (evolved Node B) that supports LTE (Long Term Evolution) communication, and an RNC (Controls NodeB and NodeB that supports wireless communication defined as so-called 3G communication in 3GPP). Radio Network Controller).

The MME 22 and the SGSN 24 may be referred to as a CPF (C-Plane Function) entity (hereinafter, referred to as CPF). The MME 22 and the SGSN 24 are devices that mainly perform mobility management of the UE 42, a bearer setting request, a bearer setting instruction, a bearer deletion request, or a bearer deletion instruction.

The AS 32 and SCS 34 are devices used to provide application services to the UE 42. The application service may be paraphrased as an IoT service. The AS 32 or SCS 34 sends the Non-IP data to the SCEF 10. The AS 32 may directly send the Non-IP data to the SCEF 10 without going through the SCS 34. AS32 or SCS34 may be described as AS32/SCS34 or SCS34/AS32 in the following description.

The SCEF 10 transmits the Non-IP data transmitted from the SCS 34/AS 32 to the MME 22 or SGSN 24. The MME 22 or SGSN 24 delivers the Non-IP data to the UE 42 via the RAN 26. The MME 22 or the SGSN 24 returns the Non-IP data to the SCEF 10 when the UE 42 is unreachable. The SCEF 10 buffers the Non-IP data that has not been delivered to the UE 42.

Further, FIG. 2 shows a configuration in which the SCEF 10, the MME 22, the RAN 26, and the SGSN 24 belong to HPLMN (Home Public Land Mobile Network). On the other hand, when SCEF10 belongs to HPLMN and MME22, SGSN24, and RAN26 belong to VPLMN (Visited PLMN), IWK(Interworking)-SCEF is arranged between SCEF10 and MME22, and further between SCEF10 and SGSN24. May be. The IWK-SCEF is arranged in the VPLMN and relays the communication between the SCEF 10 and the MME 22, and further the communication between the SCEF 10 and the SGSN 24.

Subsequently, a flow of processing when the UE 42 is unreachable will be described with reference to FIG. In FIG. 3, the SCEF 10 describes the process of delivering the Non-IP data via the MME 22, but the SGSN 24 may be used instead of the MME 22.

First, the SCS 34/AS 32 sends a NIDD Submit Request message to the SCEF 10 (S11). The NIDD Submit Request message includes an External Identifier or MSISDN (Mobile Subscriber Integrated Service Digital Network Number). Further, the NIDD Submit Request message includes SCS/AS Reference ID and Non-IP data. The External Identifier and MSISDN are identification information of the UE 42. The SCS/AS Reference ID is identification information of the SCS 34 or AS 32.

Next, when the SCEF 10 receives the NIDD Submit Request message from the SCS 34/AS 32, the SCEF 10 confirms whether the SCEF EPS bearer context associated with the External Identifier or MSISDN exists (S12). Further, when the SCF 10 receives the NIDD Submit Request message from the SCS 34/AS 32, it confirms whether the SCS 34/AS 32 is authorized to transmit the NIDD Submit Request message (S12). Further, upon receiving the NIDD Submit Request message from the SCS34/AS32, the SCEF10 confirms whether or not at least one of the allowable communication amount and the rate of the Non-IP data permitted by the SCS34/AS32 is exceeded (S12). .. The allowable communication amount may be, for example, a cumulative value of the amount of data transmitted per day.

The SCEF EPS bearer context is information indicating that a bearer for transmitting Non-IP data is established between the MME 22 and the SCEF 10. T6a is defined as a reference point in 3GPP between the MME 22 and the SCEF 10. The bearer between MME22 and SCEF10 is established at the time of Attach processing of UE42. Moreover, SGSN24 may be used instead of MME22. T6b is defined as a reference point in 3GPP between the SGSN 24 and the SCEF 10. The SCEF EPS bearer of the UE 42 is a bearer set between the SCEF 10 and the MME 22 for transmitting Non-IP data between the UE 42 and the SCS 34/AS 32.

The SCEF 10 does not have the SCEF EPS bearer context, the SCS 34/AS 32 is not authorized to send the NIDD Submit Request message, and the SCS 34/AS 32 has allowed the allowable communication amount and rate of the Non-IP data. If at least one of the events of exceeding at least one is met, a NIDD Submit Response message is sent to the SCS 34/AS 32 (S13). In the NIDD Submit Response message, information that is the cause of sending the NIDD Submit Response message is set. The information that has caused the NIDD Submit Response message to be transmitted may be indicated by using the cause value set in the NIDD Submit Response message, for example.

The SCEF 10 may discard the Non-IP data received in step S11 if it exceeds at least one of the allowable communication volume and the rate of the Non-IP data permitted by the SCS 34/AS 32.

Further, the SCEF 10 may discard the excess Non-IP data when the allowable communication amount of the Non-IP data allowed by the SCS 34/AS 32 is exceeded. Further, if the SCEF 10 exceeds the rate of the Non-IP data permitted by the SCS 34/AS 32, some of the Non-IP data may be discarded and control may be performed so that the rate becomes the permitted rate. Good.

Further, the SCEF 10 is a process for establishing a Non-IP PDN connection with the MME managing the UE corresponding to the External Identifier or MSISDN, when the SCEF EPS bearer context associated with the External Identifier or MSISDN does not exist. May be executed.

Next, the SCEF 10 has the SCEF EPS bearer context, and is authorized to send the NIDD Submit Request message by the SCS 34/AS 32. Furthermore, the allowable communication amount of the Non-IP data allowed by the SCS 34/AS 32. And if the rate is not exceeded, the control unit 12 of the SCEF 10 determines whether or not another Non-IP data to be transmitted to the SCEF EPS bearer of the UE 42 is already buffered in the storage unit 11 (S14). .. The other Non-IP data to be transmitted to the SCEF EPS bearer of the UE 42 may be, for example, Non-IP data that has not been delivered to the UE 42.

When the control unit 12 of the SCEF 10 determines that another Non-IP data to be transmitted to the SCEF EPS bearer of the UE 42 is not buffered in the storage unit 11, the SCEF 10 transmits a NIDD Submit Request message to the MME 22 ( S15). The NIDD Submit Request message includes User Identity, EPS (Evolved Packet System) Bearer ID, SCEF ID, Non-IP data, SCEF Wait Time, and Maximum Re-transmission time. User Identity is identification information of the UE 42. The EPS bearer ID is identification information of a bearer (SCEF EPS bearer) set between the SCEF 10 and the MME 22. The SCEF ID is identification information of the SECF 10. The SCEF Wait Time is the time during which the SCEF 10 can wait for the Response message transmitted from the MME 22. The Maximum Re-transmission time is the time when the SCEF 10 can retransmit the message.

Next, when the MME 22 receives the NIDD Submit Request message, the MME 22 detects that the UE 42 is unreachable (S16). Next, the MME 22 sends a NIDD Submit Response message to the SCEF (S17). The NIDD Submit Response message includes Cause and Requested Re-transmission Time. The cause is that the non-IP data is not delivered to the UE 42 because it is temporarily unreachable because the UE 42 is in the power saving mode, and further, the MME 22 indicates that the UE is reachable. When detected, the content indicating that the MME 22 notifies the SCEF 10 of that (NIDD Submit Indication) is set.

The Requested Re-transmission Time indicates the time when it is predicted that the SCEF 10 will be able to retransmit the downlink data to the UE 42 that is currently unreachable.

Further, when the MME 22 detects that the UE is reachable, the MME 22 sets a Not Reachable for NIDD flag indicating that the MME 22 notifies the SCEF 10 of that fact.

Next, when the SCEF 10 receives the NIDD Submit Response message from the MME 22, it refers to the Cause value indicating that the UE 42 is temporarily unreachable because it is in the power saving mode, and understands that the UE 42 is unreachable. To do. Further, the SCEF 10 buffers the Non-IP data which is tried to be transmitted in step S15 (S18). When the SCEF 10 determines in step S14 that another Non-IP data to be transmitted to the SCEF EPS bearer of the UE 42 is already buffered in the storage unit 11, the SCEF 10 executes the processes of steps S15 to S17. Instead, the Non-IP data received in step S11 is buffered (S18).

Next, the SCEF 10 transmits a NIDD Submit Response message including the result received from the MME 22 to the SCS 34/AS 32 (S19). Alternatively, the NIDD Submit Response message may include information indicating that the SCEF 10 has buffered the Non-IP data received in step S11 without transmitting it to the MME 22, or temporarily because the UE 42 is in the power saving mode. It may include information indicating that it is not reachable.

Next, the flow of processing when the UE 42 is reachable will be described with reference to FIG. First, the MME 22 detects that the UE 42 is reachable or is about to reach (S21). For example, the MME 22 detects that the UE 42 is reachable when the UE 42 returns from the power saving mode by executing TAU (Tracking Area Update), or when the Mobile Originated communication is started.

Next, the MME 22 sends a NIDD Submit Indication message to the SCEF 10 that sent the NIDD Submit Response message in step S17 of FIG. 3 (S22). The NIDD Submit Indication message includes User Identity. User Identity is identification information of the UE 42.

Next, upon receiving the NIDD Submit Indication message from the MME 22, the SCEF 10 transmits the buffered Non-IP data to the MME 22 using the NIDD Submit Request message in the buffered order (S23). For example, when the SCEF 10 determines in step S14 of FIG. 3 that another Non-IP data to be transmitted to the SCEF EPS bearer of the UE 42 is already buffered in the storage unit 11, it is already buffered. Non-IP data is transmitted to MME22. After that, the SCEF 10 transmits the Non-IP data received in step S11 of FIG. 3 to the MME 22.

Also, the SCEF 10 performs communication so as not to exceed the allowable communication amount and rate of the Non-IP data permitted by the SCS 34/AS 32 when transmitting the Non-IP data to the SCEF EPS bearer of the UE 42 toward the MME 22. Apply quantity and rate control. That is, the SCEF 10 applies the communication amount and the rate control not only when transmitting the Non-IP data to the MME 22 in step S15 of FIG. 3 but also when transmitting the Non-IP data in step S23 of FIG. ..

Next, upon receiving the NIDD Submit Request message, the MME 22 delivers the Non-IP data to the UE 42 (S24). For example, if the C-Plane connection is being established between the UE 42 and the MME 22, the MME 22 immediately transmits the Non-IP data to the UE 42. If the C-Plane connection is not being established between the UE 42 and the MME 22, the paging process for calling the UE 42 is performed. When the MME 22 establishes the C-Plane connection with the UE 42 by performing the paging process, the MME 22 transmits the Non-IP data to the UE 42.

Next, when the MME 22 can start the delivery of the Non-IP data in step S24, it transmits a NIDD Submit Response message to the SCEF 10 (S25). The NIDD Submit Response message includes a cause value indicating that delivery of Non-IP data could be started. Further, the SCEF 10 transmits the NIDD Submit Response message received from the MME 22 to the SCS 34/AS 32 (S26).

The operations of steps S23 to S26 are repeatedly performed according to the number of buffered Non-IP data. That is, the SCEF 10 transmits the NIDD Submit Request message to the MME 22 for each buffered Non-IP data.

Further, in step S23, the SCEF 10 transmits the Non-IP data to the MME 22, and instead of the allowable communication amount and rate of the Non-IP data permitted by the SCS 34/AS 32, the SCEF 10 allows the Non-IP data. -The communication amount and rate may be controlled so as not to exceed the allowable amount and rate of IP data.

As described above, the SCEF 10 according to the second embodiment of the present invention can determine whether the Non-IP data to be transmitted to the UE 42 is buffered. Further, when the SCEF 10 determines that the Non-IP data to be transmitted to the UE 42 is buffered, it buffers the Non-IP data without performing the transmission processing of the NIDD Submit Request message and the reception processing of the NIDD Submit Response message. can do. As a result, it is possible to prevent unnecessary traffic from occurring between the SCEF 10 and the MME 22.

Further, when the SCEF 10 sends the buffered Non-IP data to the MME 22 and sends it to the SCEF EPS bearer of the UE 42, the previously buffered Non-IP data is directed to the MME 22 to the SCEF EPS bearer of the UE 42. Can be sent. As a result, it is possible to prevent the UE 42 from reversing the order of receiving Non-IP data. As a result, it is possible to provide an application service that requires maintaining the order of Non-IP data.

Further, when the SCEF 10 sends the buffered Non-IP data to the MME 22 and sends it to the SCEF EPS bearer of the UE 42, the allowable communication amount and rate of the Non-IP data allowed by the SCS 34/AS 32 or SCEF 10 Traffic and rate control can be applied so as not to exceed. As a result, burst transfer can be avoided when the SCEF 10 retransmits Non-IP data. As a result, it is possible to reduce or avoid the event that the UE 42 such as an IoT device having a low performance in terms of communication speed fails to receive the Non-IP data.

(Embodiment 3)
Next, a flow of processing in which the SCEF 10 according to the third exemplary embodiment of the present invention receives information regarding the allowable communication amount and the rate will be described with reference to FIG. In the second embodiment, the SCEF 10 applies communication amount and rate control so as not to exceed the allowable communication amount and rate of Non-IP data allowed by the SCS 34/AS 32. On the other hand, in the third embodiment, the communication amount and the rate control are applied to the UE 42 or the SCEF EPS bearer of the UE 42 so as not to exceed the allowable communication amount and the rate of the Non-IP data. The SCEF EPS bearer of the UE 42 is a bearer set between the SCEF 10 and the MME 22 for transmitting Non-IP data between the UE 42 and the SCS 34/AS 32.

First, the SCS 34/AS 32 sends a NIDD Configuration Request message to the SCEF 10 (S31). The NIDD Configuration Request message contains the External Identifier or MSISDN. The External Identifier or MSISDN is information that identifies the UE 42. Furthermore, the NIDD Configuration Request message contains the SCS/AS Reference ID. Next, the SCEF 10 stores the External Identifier or MSISDN included in the NIDD Configuration Request message, and further the SCS/AS Reference ID in the storage unit 11 (S32).

Next, the SCEF 10 sends a NIDD Authorization Request message to the HSS (Home Subscriber Server) to confirm whether the SCS 34/AS 32 is authorized to send the received NIDD Configuration Request message regarding the External Identifier or MSISDN. Yes (S33). The NIDD Authorization Request message includes an External Identifier or MSISDN and an APN (Access Point Name) associated with the SCEF 10. The HSS is a node device that manages subscriber information regarding a plurality of UEs.

Next, the HSS determines that the SCS 34/MME 22 is authorized to send the NIDD Configuration Request message (S34). Further, the HSS extracts the IMSI (International Mobile Subscriber Identity) associated with the External Identifier or MSISDN included in the NIDD Authorization Request message. The IMSI is used as the identification information of the UE in the mobile network.

Next, the HSS sends a NIDD Authorization Response message to the SCEF 10 as a response to the NIDD Authorization Request message (S35). The NIDD Authorization Response message contains the IMSI associated with the External Identifier or MSISDN. Further, the NIDD Authorization Response message includes Load Control Information indicating at least one of the allowable communication volume and the rate of the Non-IP data permitted by the UE 42. It is assumed that the HSS manages, as subscriber information, at least one of the allowable communication volume and rate of Non-IP data permitted for each UE or each SCEF EPS bearer of the UE.

Next, the SCEF 10 transmits a NIDD Configuration Response message to the SCS 34/AS 32 as a response to the NIDD Configuration Request message (S36).

By executing the process of FIG. 5, the SCEF 10 can acquire from the HSS information indicating at least one of the allowable communication volume and the rate of the Non-IP data permitted by the UE 42. Alternatively, the SCEF 10 can acquire, from the HSS, information indicating at least one of the allowable communication amount and the rate of the Non-IP data permitted by the SCEF EPS bearer of the UE 42.

Further, the SCEF 10 can transmit the Non-IP data to the UE 42 according to the same sequence as in FIG. However, the SCEF 10 allows the UE 42 or the SCEF EPS bearer of the UE 42 to transmit the Non-IP data to the SCEF EPS bearer of the UE 42 toward the MME 22 in step S15 of FIG. 3 and step S23 of FIG. Apply traffic and rate control so as not to exceed the allowable traffic and rate of Non-IP data.

As described above, the SCEF 10 directs the buffered Non-IP data toward the MME 22 to the SCEF EPS bearer of the UE 42 when transmitting to the UE 42 or the SCEF EPS bearer of the UE 42. Traffic and rate control can be applied so as not to exceed the allowable traffic and rate of IP data. As a result, it is possible to reduce or avoid the event that the UE 42 such as an IoT device having a low performance in terms of communication speed fails to receive Non-IP data.

(Embodiment 4)
Subsequently, a configuration example of the UE 42 according to the fourth exemplary embodiment of the present invention will be described using FIG. 6. The UE 42 has a communication unit 43 and a control unit 44. The communication unit 43 and the control unit 44 may be software or modules in which processing is executed by the processor executing a program stored in the memory. Alternatively, the communication unit 43 and the control unit 44 may be hardware such as a chip or a circuit.

The communication unit 43 receives the Non-IP data delivered from the MME 22. Here, the communication unit 43 receives a plurality of Non-IP data by using one message. That is, the MME 22 does not repeat the transmission of Non-IP data the same number of times as the number of Non-IP data buffered in the SCEF 10, but transmits one message including a plurality of Non-IP data to the UE 42. The communication unit 43 outputs one message including a plurality of Non-IP data to the control unit 44.

The control unit 44 reads a plurality of Non-IP data included in one message for each Non-IP data. In other words, the control unit 44 divides the plurality of Non-IP data included in one message into individual Non-IP data and reads them. In other words, the control unit 44 parses and reads a plurality of Non-IP data included in one message.

The control unit 44 may hold, for example, information regarding the data size of the Non-IP data. For example, information regarding the data size of each Non-IP data may be set in one message including a plurality of Non-IP data. Alternatively, when the data size of the Non-IP data is predetermined in the mobile network, the control unit 44 may hold information regarding the predetermined data size of the Non-IP data. The control unit 44 may read a plurality of Non-IP data included in one message according to the data size of the Non-IP data.

Next, the flow of processing when the UE 42 is reachable will be described using FIG. 7. Steps S41 and S42 of FIG. 7 are similar to steps S21 and S22 of FIG. 4, and detailed description thereof will be omitted.

Next, when the SCEF 10 receives the NIDD Submit Indication message from the MME 22, the SCEF 10 sends the buffered non-IP data to the MME 22 using one NIDD Submit Request message to the SCEF EPS bearer of the UE 42 ( S43). For example, the SCEF 10 sets the first buffered Non-IP data in the data area near the beginning of the NIDD Submit Request message, and sets the newly buffered Non-IP data in the data area near the end of the message. You may set it.

Next, when the MME 22 receives the NIDD Submit Request message including the plurality of Non-IP data, the MME 22 delivers the plurality of Non-IP data to the UE 42 using one message (S44).

Next, when the MME 22 can start the delivery of the Non-IP data in step S44, the MME 22 sends a NIDD Submit Response message to the SCEF 10 (S45). Next, the SCEF 10 transmits a NIDD Submit Response message to the SCS 34/AS 32 for each Non-IP data (S46 and S47). For example, in step S43, the SCEF 10 transmits the first buffered Non-IP data #1 and the subsequently buffered Non-IP data #2 to the MME 22 using one NIDD Submit Request message. .. In this case, when the SCEF 10 receives the NIDD Submit Response message, it sends the NIDD Submit Response message indicating that it has delivered the Non-IP data #1 to the UE 42 in step S46, and delivers the Non-IP data #2 to the UE 42. A NIDD Submit Response message indicating that is transmitted in step S47.

As described above, the SCEF 10 delivers a plurality of Non-IP data to the MME 22 by using one NIDD Submit Request message to the SCEF EPS bearer of the UE 42 by executing the process shown in FIG. 7. You can Further, the MME 22 can deliver a plurality of Non-IP data to the UE 42 using one message. Furthermore, the UE 42 can read a plurality of Non-IP data included in one message for each Non-IP data.

As a result, the number of messages transmitted in the mobile network can be reduced, so that congestion that can occur in the mobile network can be avoided. For example, when an IoT terminal is used as the UE 42, it is assumed that a considerably large number of IoT terminals are connected to the mobile network. Therefore, when an IoT terminal is used as the UE 42, it is possible to obtain more effects of reducing the number of messages.

(Embodiment 5)
Next, a process of storing Non-IP data in the buffer according to the fifth embodiment will be described. Depending on the application, when storing multiple Non-IP data in the buffer, the Non-IP data already existing in the buffer may not be necessary, and only the Non-IP data newly stored in the buffer may be needed. ..

For example, if the Non-IP data is information indicating the state of the UE 42, only new Non-IP data may be needed. Specifically, when the UE 42 is a lamp, the Non-IP data may include information indicating whether the lamp state is ON or OFF. First, when Non-IP data indicating that the lamp state is turned ON is stored in the buffer, and then Non-IP data indicating that the lamp state is turned OFF is sent from SCS34/AS32 to SCEF10. Non-IP data stored in the buffer is unnecessary.

In such a case, the SCEF 10 may delete the Non-IP data initially stored in the buffer and buffer only the Non-IP data transmitted from the SCS34/AS32 to the SCEF 10 later.

Here, the Non-IP data stored in the buffer will be described with reference to FIGS. 8 and 9. FIG. 8 shows the Non-IP data buffered before the step S11 of FIG. 3 is transmitted. FIG. 9 shows the Non-IP data buffered in step S18 of FIG.

In the buffer order of FIGS. 8 and 9, the first buffer is the fastest buffered Non-IP data, and the third buffer is the latest buffered Non-IP data. The setting content of the Non-IP data may indicate the control content of the UE 42, for example. For example, the Non-IP data having the buffer order of 2 in FIG. 8 indicates that the switch of the device is turned on. Furthermore, it is assumed that an attribute ID is set in each Non-IP data. For example, Non-IP data having a buffer order of 2 has information indicating a lamp state set as an attribute ID.

Here, when the SCEF 10 receives the Non-IP data having the same attribute ID, the SCEF 10 may delete the already buffered Non-IP data. In FIG. 9, when the non-IP data whose buffer order is 2 and the attribute ID of the newly received non-IP data match in the lamp state, the already buffered non-IP data is deleted. It shows that it is doing.

As described above, when buffering Non-IP data, the SCEF 10 can delete unnecessary Non-IP data that is already buffered Non-IP data. As a result, the buffer size of the SCEF 10 can be reduced.

Then, below, the structural example of UE42 and SCEF10 demonstrated in the above-mentioned several embodiment is demonstrated.

FIG. 10 is a block diagram showing a configuration example of the UE 42. Radio Frequency (RF) transceiver 1101 performs analog RF signal processing to communicate with RAN 26. The analog RF signal processing performed by the RF transceiver 1101 includes frequency up conversion, frequency down conversion, and amplification. The RF transceiver 1101 is coupled with the antenna 1102 and the baseband processor 1103. That is, the RF transceiver 1101 receives modulated symbol data (or OFDM symbol data) from the baseband processor 1103, generates a transmission RF signal, and supplies the transmission RF signal to the antenna 1102. The RF transceiver 1101 also generates a baseband reception signal based on the reception RF signal received by the antenna 1102, and supplies this to the baseband processor 1103.

The baseband processor 1103 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression/decompression, (b) data segmentation/concatenation, (c) transmission format (transmission frame) generation/decomposition, and (d) transmission channel coding/decoding. , (E) modulation (symbol mapping)/demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). On the other hand, the control plane processing includes layer 1 (eg, transmission power control), layer 2 (eg, radio resource management, and hybrid automatic repeat request (HARQ) processing), and layer 3 (eg, attach, mobility, and call management). Signaling management).

For example, in the case of LTE and LTE-Advanced, digital baseband signal processing by the baseband processor 1103 includes signal processing of Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, MAC layer, and PHY layer. But it's okay. Further, the control plane processing by the baseband processor 1103 may include processing of Non-Access Stratum (NAS) protocol, RRC protocol, and MAC CE.

The baseband processor 1103 is a modem processor (eg, Digital Signal Processor (DSP)) that performs digital baseband signal processing, and a protocol stack processor (eg, Central Processing Unit (CPU)) that performs control plane processing, or a Micro Processing Unit. (MPU)) may be included. In this case, the protocol stack processor that performs the control plane processing may be shared with the application processor 1104 described below.

The application processor 1104 is also called a CPU, MPU, microprocessor, or processor core. The application processor 1104 may include a plurality of processors (a plurality of processor cores). The application processor 1104 includes a system software program (Operating System (OS)) read from the memory 1106 or a memory (not shown) and various application programs (for example, call application, WEB browser, mailer, camera operation application, music playback). Various functions of the UE 42 are realized by executing the (application).

In some implementations, the baseband processor 1103 and the application processor 1104 may be integrated on a single chip, as shown by the dashed line (1105) in FIG. In other words, the baseband processor 1103 and the application processor 1104 may be implemented as one System on Chip (SoC) device 1105. SoC devices are also sometimes referred to as system large scale integration (LSI) or chipsets.

The memory 1106 is a volatile memory or a non-volatile memory or a combination thereof. Memory 1106 may include multiple physically independent memory devices. The volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, hard disk drive, or any combination thereof. For example, the memory 1106 may include an external memory device accessible by the baseband processor 1103, the application processor 1104, and the SoC 1105. Memory 1106 may include embedded memory devices integrated within baseband processor 1103, application processor 1104, or SoC 1105. Further, the memory 1106 may include a memory within a Universal Integrated Circuit Card (UICC).

The memory 1106 may store a software module (computer program) including a command group and data for performing the processing by the UE 42 described in the above-described embodiments. In some implementations, the baseband processor 1103 or the application processor 1104 may be configured to perform the processing of the UE 42 described in the above embodiments by reading the software module from the memory 1106 and executing it.

FIG. 11 is a block diagram showing a configuration example of the SCEF 10. Referring to FIG. 11, the SCEF 10 includes a network interface 1201, a processor 1202, and a memory 1203. The network interface 1201 is used to communicate with a network node (e.g., MME 22 or SGSN 24). The network interface 1201 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.

The processor 1202 reads the software (computer program) from the memory 1203 and executes the software to perform the processing of the SCEF 10 described using the sequence diagram and the flowchart in the above embodiment. The processor 1202 may be, for example, a microprocessor, MPU, or CPU. The processor 1202 may include multiple processors.

The memory 1203 is composed of a combination of a volatile memory and a non-volatile memory. Memory 1203 may include storage located remotely from processor 1202. In this case, the processor 1202 may access the memory 1203 via an I/O interface (not shown).

In the example of FIG. 11, the memory 1203 is used to store a software module group. The processor 1202 can perform the processing of the SCEF 10 described in the above embodiment by reading these software modules from the memory 1203 and executing them.

As described with reference to FIGS. 10 and 11, each of the processors included in the UE 42 and the SCEF 10 in the above-described embodiment includes one or a plurality of instructions including a group of instructions for causing a computer to execute the algorithm described with reference to the drawings. Run the program. This program can be stored using various types of non-transitory computer readable media, and can be supplied to a computer. Non-transitory computer readable media include various types of tangible storage media. 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 disks), Compact Disc Read Only Memory (CD-ROM), CD- R, CD-R/W, semiconductor memory (for example, mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)) are included. In addition, the program may be supplied to the computer by various types of transitory computer readable media. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. The transitory 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 present invention is not limited to the above-mentioned embodiment, and can be modified as appropriate without departing from the spirit of the present invention. Further, the present invention may be implemented by appropriately combining the respective embodiments.

Although the present invention has been described with reference to the exemplary embodiments, the present invention is not limited to the above. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the invention.

This application claims the priority on the basis of Japanese application Japanese Patent Application No. 2016-199093 for which it applied on October 7, 2016, and takes in those the indications of all here.

The whole or part of the exemplary embodiments disclosed above can be described as, but not limited to, the following supplementary notes.
(Appendix 1)
A storage unit that buffers the first Non-IP data that has not been delivered to the communication terminal,
When the first Non-IP data is buffered when the second Non-IP data addressed to the communication terminal is received from the server device, the second Non-IP data is stored in the mobile network. And a control unit that suppresses transmission to the control device and buffers the second Non-IP data in the storage unit.
(Appendix 2)
The control unit is
When the second Non-IP data is received from the server device, it is determined whether or not the first Non-IP data is buffered, and the first Non-IP data is buffered. When it is determined that the second Non-IP data is buffered in the storage unit, and when it is determined that the first Non-IP data is not buffered, the second Non-IP data is transmitted to the control device. The SCEF entity of claim 1 that sends data.
(Appendix 3)
The control unit is
When the control device receives a message indicating that Non-IP data can be delivered to the communication terminal, the first and second Non-IP data buffered in the storage unit are controlled by the control unit. The SCEF entity according to appendix 1 or 2, which is transmitted to the device.
(Appendix 4)
The control unit is
The SCEF entity according to appendix 3, which transmits the Non-IP data buffered in the storage unit to the control device in the order of being buffered in the storage unit.
(Appendix 5)
The control unit is
5. The SCEF entity according to appendix 3 or 4, which sends one message including a plurality of Non-IP data buffered in the storage unit to the control device.
(Appendix 6)
The control unit is
6. The SCEF entity according to any one of appendices 3 to 5, which transmits the first and second Non-IP data to the control device so as to satisfy a communication amount or a communication rate allowed by the server device. ..
(Appendix 7)
The control unit is
When the second non-IP data addressed to the communication terminal is received from the server device and the communication amount or communication rate allowed by the server device is exceeded, the second Non-IP data is received. -The SCEF entity according to any one of appendices 1 to 6, which discards IP data.
(Appendix 8)
The control unit is
The communication terminal or the communication terminal transmits the first and second Non-IP data to the control device so as to satisfy a communication amount or a communication rate allowed for a communication bearer transmitting Non-IP data, The SCEF entity according to any one of appendices 3 to 5.
(Appendix 9)
The control unit is
When the second Non-IP data addressed to the communication terminal is received from the server device, the communication amount allowed by the communication terminal or the communication bearer for transmitting the Non-IP data, or 9. The SCEF entity according to any one of appendices 1 to 8, which discards the second Non-IP data when the communication rate is exceeded.
(Appendix 10)
The control unit is
The communication terminal or the communication terminal receives information about a communication amount or a communication rate allowed for the communication bearer for transmitting Non-IP data, from a subscriber information management device arranged in the mobile network, The SCEF entity according to attachment 8 or 9.
(Appendix 11)
The control unit is
6. The SCEF entity according to any one of appendices 3 to 5, which transmits the first and second Non-IP data to the control device so as to satisfy a communication amount or a communication rate allowed for the SCEF entity. ..
(Appendix 12)
The control unit is
When the second Non-IP data addressed to the communication terminal is received from the server device and the communication amount or communication rate permitted by the SCEF entity is exceeded, the second Non-IP data is transmitted. -The SCEF entity according to any one of appendices 1 to 11, which discards IP data.
(Appendix 13)
The control unit is
When the second Non-IP data is Non-IP data that updates the first Non-IP data indicating the state of the communication terminal, the first Non-IP data is deleted from the storage unit. The SCEF entity according to any one of appendices 1 to 12, which causes the storage unit to buffer the second Non-IP data.
(Appendix 14)
A communication unit that receives a plurality of Non-IP data buffered by the SCEF entity until the device becomes reachable as a single message via the control device when the device becomes reachable.
A communication terminal, comprising: a control unit for reading a plurality of Non-IP data included in the one message for each Non-IP data.
(Appendix 15)
Buffer the first Non-IP data that was not delivered to the communication terminal,
When the first Non-IP data is buffered when the second Non-IP data addressed to the communication terminal is received from the server device, the second Non-IP data is stored in the mobile network. The method for processing data, wherein the second Non-IP data is buffered while being suppressed from being transmitted to the control device.
(Appendix 16)
When the self-device becomes reachable, the non-IP data buffered by the SCEF entity until the self-device becomes reachable is received as one message via the control device,
A data receiving method of reading a plurality of non-IP data included in the one message for each non-IP data.
(Appendix 17)
Buffer the first Non-IP data that was not delivered to the communication terminal,
When the first Non-IP data is buffered when the second Non-IP data addressed to the communication terminal is received from the server device, the second Non-IP data is stored in the mobile network. A program that suppresses transmission to the control device and causes the computer to buffer the second Non-IP data.
(Appendix 18)
When the self-device becomes reachable, the non-IP data buffered by the SCEF entity until the self-device becomes reachable is received as one message via the control device,
A program that causes a computer to read a plurality of non-IP data included in the one message for each non-IP data.

10 SCEF
11 storage unit 12 control unit 20 control device 22 MME
24 SGSN
26 RAN
30 server device 32 AS
34 SCS
40 communication terminal 42 UE
43 communication unit 44 control unit

Claims (6)

Receives a NIDD (Non-IP Data Delivery) request that includes downlink non-IP data from the server device,
Buffer the downlink non-IP data,
Where the terminal is reachable or reachable if it receives a request for an additional NIDD containing additional downlink non-IP data from the server device while already buffering the downlink non-IP data. Buffering the additional downlink non-IP data without sending a request for a NIDD containing the additional downlink non-IP data to the controller before becoming
exposure function entity. Of the downlink non-IP data already in the buffer, delete the one corresponding to the additional downlink non-IP data,
The exposure function entity according to claim 1. The exposure function entity is
SCEF (Service Capability Exposure Function) entity,
The server device is
SCS/AS (Service Capability Server / Application Server),
The control device is
MME (Mobility Management Entity) or SGSN (Serving GPRS (General Packet Radio Service) Support Node),
The exposure function entity according to claim 1 or 2. Receives a NIDD (Non-IP Data Delivery) request that includes downlink non-IP data from the server device,
Buffer the downlink non-IP data,
Where the terminal is reachable or reachable if it receives a request for an additional NIDD containing additional downlink non-IP data from the server device while already buffering the downlink non-IP data. Buffering the additional downlink non-IP data without sending a request for a NIDD containing the additional downlink non-IP data to the controller before becoming
Method. Of the downlink non-IP data already in the buffer, delete the one corresponding to the additional downlink non-IP data,
The method of claim 4. The server device is
SCS/AS (Service Capability Server / Application Server),
The control device is
MME (Mobility Management Entity) or SGSN (Serving GPRS (General Packet Radio Service) Support Node),
The method according to claim 4 or 5.

Images