A device-communication system may receive, from a user device via a first network, communication data originating from a first device connected to the user device via a second network having a type different from that of the first network. The device-communication system may process the communication data to determine a corresponding device-management system, and may communicate further with the user device for additional identification information, if necessary. The device-communication system determines which of a plurality of device-management systems should receive the communication data and sends the data to the appropriate system.

A device-communication system may receive, from a user device via a first network, communication data originating from a first device connected to the user device via a second network having a type different from that of the first network. The device-communication system may process the communication data to determine a corresponding device-management system, and may communicate further with the user device for additional identification information, if necessary. The device-communication system determines which of a plurality of device-management systems should receive the communication data and sends the data to the appropriate system.

A method performed by an access and mobility management function (AMF), the method comprising receiving, from a User Equipment (UE), a first message including capability information related to a periodic registration timer, setting a periodic registration timer indication based on the capability information, and transmitting, to the UE, a second message including the periodic registration timer indication.

A method performed by an access and mobility management function (AMF), the method comprising receiving, from a User Equipment (UE), a first message including capability information related to a periodic registration timer, setting a periodic registration timer indication based on the capability information, and transmitting, to the UE, a second message including the periodic registration timer indication.

Methods and apparatuses for event reporting are disclosed. According to an embodiment, an access and mobility management function (AMF) entity detects a status of a terminal device changing from unreachable to reachable and sends, to a first entity, a report indicating that the terminal device is reachable. The report contains a maximum availability time until which the terminal device is expected to be reachable.

Methods and apparatuses for event reporting are disclosed. According to an embodiment, an access and mobility management function (AMF) entity detects a status of a terminal device changing from unreachable to reachable and sends, to a first entity, a report indicating that the terminal device is reachable. The report contains a maximum availability time until which the terminal device is expected to be reachable.

A method comprising configuring a user equipment in a low activity state to operate within a radio access network wherein a radio access network notification area for the user equipment is defined based on a list of logically associated radio access network paging areas, wherein each of the logically associated radio access network paging areas is a subset of a core network tracking area identified by a paging area code value which is unique within the core network associated tracking area.

A method comprising configuring a user equipment in a low activity state to operate within a radio access network wherein a radio access network notification area for the user equipment is defined based on a list of logically associated radio access network paging areas, wherein each of the logically associated radio access network paging areas is a subset of a core network tracking area identified by a paging area code value which is unique within the core network associated tracking area.

A method of handling multi-access (MA) Protocol data unit (PDU) session establishment procedure for adding a 3GPP PDN leg to an MA PDU session already established with a non-3GPP leg is proposed. In one novel aspect, for a 5GS MA PDU session already established on non-3GPP access, upon receipt of an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message for establishing a PDN connection as a user-plane resource for the MA PDU session over 3GPP access, the UE sends an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message if any value of at least one of the critical parameters, including the PDN type, ESM cause, PDN address, S-NSSAI, SSC mode (set to SSC mode 1), and APN IEs in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message does not match/sync/compatible to the corresponding stored value of the MA PDU session with a non-3GPP leg.

A method of handling multi-access (MA) Protocol data unit (PDU) session establishment procedure for adding a 3GPP PDN leg to an MA PDU session already established with a non-3GPP leg is proposed. In one novel aspect, for a 5GS MA PDU session already established on non-3GPP access, upon receipt of an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message for establishing a PDN connection as a user-plane resource for the MA PDU session over 3GPP access, the UE sends an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message if any value of at least one of the critical parameters, including the PDN type, ESM cause, PDN address, S-NSSAI, SSC mode (set to SSC mode 1), and APN IEs in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message does not match/sync/compatible to the corresponding stored value of the MA PDU session with a non-3GPP leg.