SYSTEMS AND METHODS FOR FACILITAING MACHINE-TO-MACHINE COMMUNICATIONS - Patent application

Abstract

The present disclosure provides systems and methods that facilitate the establishment of effective machine to machine (M2M) communications in a network. The systems and methods may provide a set of instructions for providing efficient and effective communications between two or more machines by a converge telephony application server (CTAS) operably coupled to a next generation telecommunications network without loss of information.

Description

[Technical field]

[0001] Reservation of Rights Portions of the disclosure of this patent document contain material that is subject to intellectual property rights, such as, but not limited to, copyright, designs, trademarks, IC layout designs, and / or trade dress protection, owned by Jio Platforms Limited (JPL) or its affiliates (hereinafter referred to as the Owner). The Owner has no objection to the complete reproduction by anyone of the patent document or patent disclosure as it appears in the Patent and Trademark Office files and records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the Owner. This patent document includes systems and methods defined in 3GPP® Technical Specifications (TS).

[0002] The present invention relates generally to telecommunications systems, and more particularly to next generation machine-to-machine communications. [Background technology]

[0003] The following description of related art is intended to provide background information regarding the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, this section should be understood as being used only to enhance the reader's understanding of the present disclosure and not as an admission of prior art.

[0004] In recent years, cooperative communication between a large number of intelligent systems over either mobile or fixed networks has become very important. As a result, machine-to-machine (M2M) communication has emerged as one of the new areas. M2M communication describes a style of communication in which two or more entities, such as devices / machines, communicate with each other autonomously. M2M communication plays a promising role in enabling the Internet of Things (IoT) vision by providing ubiquitous connectivity among a large number of intelligent devices. The term M2M in IoT describes the autonomous information exchange among a large number of devices that are interconnected with each other. Thus, M2M communication covers a wide range of use cases. For example, application areas of M2M include ITS (intelligent transportation system), logistics and supply chain management, smart metering, e-healthcare, surveillance and security, smart city, and home automation. In particular, many intelligent devices are expected to be introduced in the automotive field, security, e-healthcare, and logistics. As a result, M2M communication is expected to reshape the business / revenues of telecom operators, M2M enterprises, and M2M enablers, owing to the emerging use of intelligent sensors and actuators in many of the advanced applications mentioned above.

[0005] Nevertheless, M2M communications pose significant challenges to mobile networks due to the expected large number of devices accessing simultaneously to transmit small data sizes and a diverse range of applications.

[0006] Therefore, there is a need in the art for an effective and economical system and method that can overcome the aforementioned problems in the art and efficiently enable faster and more efficient next generation based M2M (Machine to Machine) communications. Summary of the Invention [Problem to be solved by the invention]

[0007] Some of the objectives of the present disclosure that are met by at least one embodiment herein are listed herein below.

[0008] It is an object of the present disclosure to facilitate efficient parallel and improved communication between two or more machines.

[0009] An objective of this disclosure is to enable machines to initiate and receive calls.

[0010] It is an object of the present invention to provide efficient and effective communication between two or more machines without loss of information. [Means for solving the problem]

[0011] This section is provided to introduce certain objects and aspects of the invention in a simplified form, which are further described below in the Detailed Description. This Summary is not intended to identify key features or the scope of the claimed subject matter.

[0012] In order to achieve the aforementioned objectives, the present invention provides a system and method for facilitating machine to machine (M2M) communication in a network. The system may include at least one converge telephony application server (CTAS) in communication with one or more network devices associated with the network and a centralized database. The at least one CTAS may be operably coupled to a processor, which may further be coupled to a memory, the memory storing instructions, which upon execution of the instructions, cause the at least one CTAS to receive one or more predefined request signals from a network device having a predefined M2M number, identify whether the predefined M2M number belongs to a set of unique numbers based on a set of predefined instructions, cause only the set of unique numbers to utilize a plurality of services associated with the M2M communication, and based on the identification, invoke a call leg to initiate communication with each of the plurality of services, and based on the invoked call leg, establish simultaneous communication between the network device and the plurality of services by the centralized server.

[0013] In one embodiment, the CTAS may be further configured to capture call services at the first database and message services at the second database during the invoked call leg.

[0014] In one embodiment, the M2M number has a predefined length, which includes a Mobile Station International Subscriber Directory Number (MSISDN) ID and a respective country code.

[0015] In one embodiment, the set of unique numbers is stored in a database, each number in the set of unique numbers is associated with a unique user ID, and the set of unique numbers is given permissions for incoming and outgoing calls.

[0016] In one embodiment, the set of unique numbers is stored in a predefined format including international IDs, mobile numbers, and fixed line numbers.

[0017] In one embodiment, the database contains predefined identity numbers associated with predefined services in a set of unique numbers.

[0018] In one embodiment, if no identity is defined in a given service, the M2M number is allowed to access the given service and incoming calls from any number to the M2M number are allowed.

[0019] In one embodiment, the M2M number has a predefined registration and call flow process.

[0020] In one embodiment, a predefined caller ring back tone (CRBT) service is applicable to the M2M number.

[0021] In one embodiment, one or more predefined services flag predefined instances that are related to the one or more predefined services as not being able to be associated with the M2M number.

[0022] In one embodiment, roaming facilities are not available for M2M numbers in any network.

[0023] In one embodiment, when a network device with an M2M number dials any valid number, the CTAS checks the called party number in a database, and if a valid number is found in the database, the CTAS provides call routing processing.

[0024] In one embodiment, if a network device with an M2M number dials any invalid number, the call is rejected with an error code.

[0025] In one embodiment, if an outgoing call is barred to an M2M number, the CTAS responds with a decline with a predefined announcement, which is mapped with a predefined internal cause code.

[0026] In one embodiment, when a network device associated with the entity dials an M2M number on the originating leg, the CTAS queries the Mobile number portability (MNP) of the dialed M2M number.

[0027] In one embodiment, the query to the MNP returns the domain name of the M2M subscriber, and if no LRN (location routing number) is returned by the MNP, the CTAS does not provide the NPRI (Network-Provided-Routing-Information) to the centralized database.

[0028] In one embodiment, if the M2M number belongs to the second entity, the MNP query is skipped and the CTAS routes the call to a predefined service.

[0029] In one embodiment, certain priority services are available to network devices that have an M2M number.

[0030] In one embodiment, if the M2M user is not registered or is unreachable, the CTAS does not perform a CSRN (CS Domain Routing Number) query.

[0031] In one aspect, a method is for facilitating machine to machine (M2M) communication in a network of entities. The method can include receiving, by at least one converge telephony application server (CTAS), one or more predefined request signals from a network device having a predefined M2M number. In one embodiment, the CTAS communicates with one or more network devices associated with the network and a centralized database. The method can further include identifying, by the CTAS, whether the predefined M2M number belongs to a unique set of numbers based on a predefined set of instructions. In one embodiment, only the unique set of numbers utilizes a plurality of services associated with the M2M communication. The method can further include invoking, by the CTAS, a call leg to initiate communication with each of the plurality of services based on the identification, and establishing, by the centralized server, simultaneous communication with the network device and the plurality of services based on the invoked call leg.

[0032] In one aspect, a user equipment (UE) may be communicatively coupled to at least one converge telephony application server (CTAS), where the coupling of the CTAS may include receiving a connection request from the UE to dial an M2M number, sending an acknowledgement of the connection request to the CTAS, and transmitting a plurality of signals in response to the connection request.

[0033] In one aspect, a non-transitory computer-readable medium including machine-executable instructions executable by a processor may be configured to receive one or more predetermined request signals from a network device having a predetermined M2M number, identify based on a predetermined set of instructions whether the predetermined M2M number belongs to a group of unique numbers, where only the unique group of numbers utilize a plurality of services related to M2M communication, invoke call legs to initiate communication with each of the plurality of services based on the identification, and further establish simultaneous communication between the network device and the plurality of services via a centralized server based on the invoked call legs.

[0034] The accompanying drawings, which are incorporated herein and constitute a part of the present invention, illustrate exemplary embodiments of the disclosed method and system, with like reference numerals referring to the same parts throughout the different drawings. The components in the drawings are not necessarily drawn to scale, emphasis instead being placed on clearly illustrating the principles of the invention. Some drawings may use block diagrams to illustrate components and may not represent the internal circuitry of each component. Those skilled in the art will appreciate that the inventions in such drawings include inventions in electrical components, electronic components, or circuits commonly used to implement such components. [Brief description of the drawings]

[0035] [Figure 1A] 1 illustrates an exemplary network architecture in which or with which the system of the present disclosure may be implemented, according to one embodiment of the present disclosure. [Figure 1B] 1 illustrates an exemplary network architecture in which or with which the system of the present disclosure may be implemented, according to one embodiment of the present disclosure. [Figure 2A] Referring to FIG. 1A, an exemplary representation of a network device is shown, according to one embodiment of the present disclosure. [Figure 2B]Referring to FIG. 1A, an exemplary representation of a network device is shown, according to one embodiment of the present disclosure. [Diagram 3] 1 illustrates an example representation of a flow diagram for facilitating machine to machine (M2M) communication in a network associated with an entity, according to one embodiment of the present disclosure. [Figure 4] An exemplary computer system in or by which embodiments of the present disclosure may be utilized is shown, in accordance with the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0036] The above will become more apparent from the following more detailed description of the invention.

[0037] In the following description, for the purpose of explanation, various specific details are set forth to provide a thorough understanding of the embodiments of the present invention. However, it will be apparent that the embodiments of the present disclosure may be practiced without these specific details. Each of the several features described below can be used alone or in any combination with other features. Individual features may not address all of the above problems, or may address only some of the above problems. Some of the above-described problems may not be fully addressed by any of the features described herein.

[0038] The following description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the following description of exemplary embodiments will provide those skilled in the art with a helpful description for implementing the exemplary embodiments. It will be understood that various changes can be made in the function and arrangement of elements without departing from the spirit and scope of the invention as described.

[0039] In the following description, specific details are provided to provide a thorough understanding of the present embodiments. However, it will be understood by those skilled in the art that some embodiments may be practiced without these specific details. For example, components such as circuits, systems, networks, processes, etc. may be shown as components in block diagram form in order to avoid obscuring the embodiments in unnecessary detail. In other examples, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0040] The systems and methods of the present invention facilitate overcoming the above-mentioned problems by enabling effective machine to machine (M2M) communications to be established in a network. The systems and methods can provide a set of instructions for providing efficient and effective communications between two or more machines without loss of information.

[0041] 1A-1B illustrate exemplary network architectures 100 and 120 in which the system of the present disclosure may be implemented or with which the system of the present disclosure may be implemented, according to an embodiment of the present disclosure. As shown in the representation 100 in FIG. 1A, a network device 102 (hereinafter the network device is interchangeably referred to as a converged telephony application server or CTAS 102) may be configured to facilitate communication between multiple machine to machine (M2M) devices (110-1, 110-2, 110-3, ... 110-N) (hereinafter collectively referred to as M2M devices 110 or individually as M2M devices 110). The M2M devices may include one of a user device, user equipment, automotive vehicle, smart home appliance, industrial smart appliance, web, mobile phone, tablet computer, personal digital assistant (PDA), personal computer (PC), laptop computer, media center, workstation, and other such devices. The network device 102 may be configured as an application server, may be communicatively operable, or may be integrated with an Internet Protocol Multimedia Subsystem (IMS) server 106 (also interchangeably referred to as an IMS or IMS core). The IMS server 106 may be associated with a vendor or service provider that enables the user device 110 to establish simultaneous communications with multiple emergency services. In one embodiment, the CTAS or network device 102 may be implemented with an existing IMS implementation to facilitate network services corresponding to the communication network 112. In one example, the communication network 112 may be associated with, for example, a fifth generation (5G) network service.

[0042] The M2M device 110 may be at least one of a wired device or a wireless device and may be associated with an M2M number.

[0043] In one embodiment, the communication network 112 associated with the CTAS-based IMS implementation may be a 5G network, which may include at least one of a wireless network, a wired network, or a combination thereof. The communication network 112 may be implemented as one of different types of networks, such as an intranet, a local area network (LAN), a wide area network (WAN), the Internet, etc. Furthermore, the network may be either a dedicated network or a shared network. A shared network may represent an association of different types of networks that may use different protocols, such as, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol / Internet Protocol (TCP / IP), Wireless Application Protocol (WAP), Automatic Repeat Request (ARQ), etc. In one embodiment, the communication network 112 may relate to a 5G network, which may be facilitated over a terrestrial wide area access network, such as a Global System for Mobile Communications (GSM) network, a universal terrestrial radio network (UTRAN), an Enhanced Data rate for GSM Evolution (EDGE) radio access network (GERAN), an evolved universal terrestrial radio access network (E-UTRAN), a WIFI or other LAN access network, or a satellite or wireless microwave access (WIMAX) network. In an exemplary embodiment, the communication network may enable a 5G or 6G network based on a subscription for a user / user device and / or via a Subscriber Identity Module (SIM) card. Various other types of communication networks or services may be possible.

[0044] In one example, the communications network 112 may utilize different types of air interfaces, such as code division multiple access (CDMA), time division multiple access (TDMA), or frequency division multiple access (FDMA) air interfaces, and other implementations. In an exemplary embodiment, wired user devices may use wired access networks alone or in combination with wireless access networks, including, for example, plain old telephone service (POTS), public switched telephone network (PSTN), asynchronous transfer mode (ATM), and other network technologies configured to transport Internet Protocol (IP) packets.

[0045] As shown in FIG. 1B, in one example, the CTAS (102) may be a session initiation application (SIP) server that is a 3GPP and RFC-compliant implementation of the LTE service architecture. The CTAS is at the center of the voice core network (120) and manages the implementation of connectivity and auxiliary services between subscribers. Furthermore, the CTAS (102) can be operatively coupled to a call session control function (E-CSCF) that controls all services in the all-IP network and enables new subscriber services such as VoLTE, VoWiFi, RCS, and WebRTC. An Ro interface-based online charging (OCS) (168) can be implemented in the telecom network. One or more charging data records (CDRs) generated by an application server, such as the CTAS, can be used by the mediation system (170) for reconciliation purposes. Additionally, the CTAS (102) may be operatively coupled to a call forwarding vertex (CFX) (122) that controls all services within the all-IP network and enables new subscriber services such as VoLTE, VoWiFi, RCS, and WebRTC. For example, the CFX may act as a central control core that may provide session and service control using predefined interfaces and application trigger mechanisms. One or more access elements, as well as clients such as VoLTE devices and operator 4G voice clients (166), may be further associated with the CTAS (102).In one example, the CTAS (102) may be further coupled to an Element Management System (EMS) capable of managing a particular type of one or more network elements (172, 174, 176) in a telecommunication management network (TMN). Additionally, a Centralised Data Layer (CDL) (104) may be operatively coupled to the CTAS (102). In one example, the CDL may maintain a mapping table between ECIs and Short-Distance Charging Areas (SDCAs) of the circle. During the application commissioning process, the CDL instance of the circle (MNC) downloads the mapping table of cell ids to SDCAs of the circle (MNC) from the centralised database. In one example, the UtGW (NAF and BSF) (114) provides a gateway to one or more networks to provide application independent functionality for mutual authentication of mutually unknown user equipment and servers, and to "bootstrap" the subsequent exchange of session secret keys. This allows the use of additional services such as Mobile TV and PKI, which require authentication and secure communication. For example, the BSF is introduced by an application server (NAF) after an unknown UE device tries to obtain service access. The NAF queries the UE to the BSF. The UE and the BSF authenticate each other via the 3GPP protocol AKA (Authentication and Key Agreement) and the BSF sends a related query to the Home Subscriber Server (HSS). After that, the UE and the BSF share a session key that is used for encrypted data exchange with the application server (NAF). When the UE reconnects to the NAF, the NAF can obtain the session key as well as the user-specific data from the BSF and can start data exchange with the end device (UE) using the session key related to encryption.

[0046] The IMS server (106 in FIG. 1A and FIG. 1B) may include one or more modules or components that may enable the execution of one or more functions. For example, the IMS server may be an existing IMS core that includes components / modules that handle various functions, such as a serving call session control function (S-CSCF) module 124, an interrogating call session control function (I-CSCF) module 126, and a proxy call session control function (P-CSCF) module 128. In one embodiment, the CTAS 102 may include a telephony application server (TAS), which may be integrated with the IMS core and a network of other application servers to provide network services, such as a fifth generation (5G) network, and may be considered a common component used in communication networks to provide telephony applications and additional multimedia capabilities. In another example, the other application server may include a mobile number portability (MNP) server 158 that may provide number portability to users, such as allowing them to keep the same number when changing service providers. In yet another example, another application server may include a Short Message Service Center (SMSC) (154) that may store, forward, convert, and deliver Short Message Service (SMS) messages. Various other servers may be integrated into a CTAS-enabled IMS implementation to enable one or more services related to a communications network or a 5G network.

[0047] In one embodiment, the network device or CTAS 102 may be communicatively coupled or integrated with one or more functional components, such as, for example, a Session Initiation Protocol (SIP)-based application server.

[0048] Further, as shown in FIG. 1B, to provide various aspects of network services (such as 5G networks), the IMS server components (S-CSCF, I-CSCF modules, etc.) may also include function-related components / modules, such as a breakout gateway control function (BGCF) module 128, a media gateway control function (MGCF) module 164, an interconnection border control function (IBCF) 134, and other components / modules. In a typical implementation, the BGCF module 128 may enable routing of call signaling to and from the most appropriate S-CSCF module 124. In a current implementation, the BGCF module 128 may enable routing of the call to the respective CTAS 102 to establish the routing of the L1 number. Furthermore, the CFX module (122) may include an emergency call session control function (130). The E-CSCF (130) is a specialist platform designed to facilitate support of emergency service dialing. In this capacity, the E-CSCF takes requests from the P-CSCF (132) and S-CSCF (124) and routes these emergency session requests to the appropriate next destination, such as a Public Safety Answering Point (PSAP). More generally, the MGCF module 164 may be a SIP endpoint that can interface with a Security Gateway (SGW) and also control resources in the Media Gateway (MGW) 166. The IBCF module 134 may enable border control between various service provider networks, thus providing CTAS-enabled IMS network security with respect to signaling information.The IMS server may also include other existing components, such as components related to Mobile Communications on board Aircraft (MCA) (160), which allows passengers to use their mobile phones on the aircraft. A small cellular network is provided on the aircraft, to which mobile phones can be connected. In addition, as shown in FIG. 1B, for a CTAS-IMS based implementation, it may be associated with another application server, such as a Caller Ring Back Tone (CRBT) server (152), which allows callers to hear a subscriber-predefined song or audio clip instead of the standard ring tone until the subscriber answers the call.

[0049] In one embodiment, the CTAS (102) may be able to handle VoLTE, M2M, fixed line (FLP), and enterprise subscribers simultaneously. This makes the CTAS a unique type of TAS that gives operational and engineering advantages in managing subscriber growth in the VoLTE, fixed and enterprise domains in the most efficient way. In another embodiment, the CTAS (102) can be integrated with the NSN CSCF to deliver MMTel supplementary services to VoLTE customers as well as customers using 4G voice clients over LTE or WiFi. The CTAS can support subscriber online and offline charging. The CTAS (102) can further include an IP Short Message Gateway (IPSMGW) that can handle SIP-based messaging services for IMS subscribers. Additionally, the IP-SM-GW interacts with the legacy SMSC (154) using MAP signaling to enable IMS to SMS conversion and delivery. Additionally, the CTAS (102) may include, but is not limited to, a service Centralization and Continuity Application Server (SCC AS), which may function as a back-to-back user agent (B2BUA) within the IMS architecture and facilitate service centralization as well as coordination of Single Radio Voice Call Continuity (SR-VCC) handover procedures.

[0050] The system can facilitate simultaneous communication through a combination of hardware and software implementation. FIG. 2A illustrates an example representation of a network device according to one embodiment of the present disclosure, with reference to FIG. 1A. The system includes a network device or CTAS 102, which can include one or more processors. The network device or CTAS 102 can be integrated with an IMS server 106 to provide network services to the user device 110 (as shown in FIG. 1A). In an aspect, the network device 102 can include one or more processor(s) 202 connected to a memory 204. The memory 204 can store instructions that, when executed by the one or more processors, can cause the system to perform steps described herein. The network device or CTAS 102 can cause the system to receive a request to route an M2M number in anticipation of at least one incoming communication from a UE (102) via an IMS (106 in FIG. 1A).

[0051] In one example, one or more CTAS instances may be deployed in a super core of a network architecture. Each CTAS instance may be dedicated to handling traffic for a given circle. Furthermore, multiple CTAS clusters may be used to serve traffic for a single circle, and each circle may have its own CDL module. In one embodiment, the CTAS (102) may be configured to store a set of M2M numbers (referred to herein simply as M2M numbers) that may be authorized to initiate and receive calls between at least four endpoints of at least two circles, such as Circle A or Party A and Circle B or Party B.

[0052] The system can support: At least four B-party numbers, e.g. 10-digit mobile / fixed numbers for outgoing calls originating from A-circle 13-digit IoT numbers. At least four A-party numbers, e.g. 10-digit mobile / fixed numbers of incoming calls to a 13-digit IoT number in B-circle At least 4 B-party numbers i.e. 10 digit mobile / fixed numbers for outgoing SMS calling from A-circle 13 digit IoT numbers At least 4 A-party numbers (10-digit mobile / fixed numbers) with incoming SMS to B-circle 13-digit IoT numbers

[0053] In one example, the number may be unique and configurable with a set of instructions for MACD (Move, Add, Change, or Delete). The M2M number may apply to all 13-digit MSISDNs (Mobile Station International Subscriber Directory Numbers) provided to the user or may be unique for each 13-digit MSISDN. In one example, the M2M number may be mobile and fixed-line. In one example, the 10-digit mobile number configured for restricted voice and SMS calls may be a local or international number according to current telecommunications regulations. Any number not belonging to the following groups may be an invalid number:

[0054] In one example, peer-to-peer (P2P) services will work for 13-digit numbers even while roaming. If the P2P service (voice and SMS) template does not define a B-party number for the 13-digit MSISDN, P2P services will be prohibited. P2P services, if required for NB-IoT in the future, will be raised as a separate requirement, per the MACD instruction set.

[0055] In one example, the M2M number may be in a predefined format. For example, the predefined numbering format may be "+ <cc> <msisdn>", but is not limited to this.

[0056] Additionally, an M2M number may include multiple services: One or more operator participation services may not be applicable to M2M / IoT. In an example implementation, announcements may be requested for one or more blocked calls on an M2M number, for both incoming and outgoing calls. ·A set of standard cause codes for voice, SMS and CRBT services may be applicable to M2M numbers. Supplementary services such as call forwarding, conference calling, call waiting, call hold and missed call notification are prohibited for M2M subscribers. The network must support call hold requests initiated from other devices to M2M users. International roaming may be prohibited for M2M numbers. · Mobile number portability (MNP) may not be applicable to M2M numbers of a second operator set that is not associated with the network. OFFNET M2M numbers may be routed to a second set of operators without a Location Routing Number (LRN). · M2M devices will follow 3GPP / GSMA specifications for VoLTE registration and call / SMS services. · Video call service is not applicable to M2M numbers. Priority Service (Multimedia Priority Service) can be applied to M2M numbers. · The ban on calls / SMS if and when implemented by the Appellate Authority (DoT) on VoLTE will also be applicable on M2M numbers. 13-digit M2M / IoT numbers will be allowed to call emergency numbers such as police, fire, and ambulance. A2P (Application to peer) transaction / promotion messages are allowed on long code, short code, and CLI (calling line identification) M2M numbers.

[0057] In one embodiment, the CTAS (102) may be configured to determine the calling and called parties based on local settings where the M2M number sequence may be defined as mobile or PSTN. For M2M number identification, the CTAS (102) may utilize multi-channel hybrid medium access control (MCHM) and multi charging hybrid function (MCHF). MCHM may refer to M2M users of a given network and MCHF may refer to M2M users of a second operator set. The minimum and maximum length of MSISDN (Mobile Station International Subscriber Directory Number) for M2M users may be a predefined number. For example, MSISDN number may be 15 including country code.

[0058] In one embodiment, the CTAS (102) can store M2M data in a repository including a list of authorized user identities, and incoming and outgoing calls between authorized user identities can be allowed. In one example, the user identities may be stored in an international format, but are not limited to such. The user identities defined in each subtree may be different. In one embodiment, at least a unique number may be configured for each subtree. For example, up to 16 unique identities in total may be defined. Alternatively, if there is no user identity defined in a given service, such as, but not limited to, an incoming allowed number in voice data, the M2M number may be allowed to access the given service. For example, incoming calls to the M2M number may be allowed from any number.

[0059] In one example, the registration and call flow for M2M numbers may be the same as for VoLTE subscribers. The CTAS may issue an update request to the M2M device. The storage class may include information about requirements for secure storage of data on the device. After authenticating and ensuring that the M2M device is authorized to issue the request, the CTAS may execute the request. The CTAS may further check the parameters of the request and store the request on the M2M device, otherwise an exception may be returned. The result of the update operation may be returned to the CTAS. The status parameter may indicate that the execution of the actual operation is delayed.

[0060] When the M2M device connects back to the M2M network (e.g., when it wakes up), it can get the pending requests from the INBOX and process them. A call flow can be associated with each message. Status indications can be created by a trusted entity in the device / gateway and can be unique and verifiable.

[0061] In one embodiment, the CTAS (102) may be coupled to a given CRBT server. This CRBT server may provide one or more CRBT services to the M2M number. In one example, if the M2M number uses a CRBT service, the Nat-ss-code value may be E.

[0062] In one embodiment, by setting both operator and user flags as false in the MMTel-Service-Extra XML, multiple supplementary services except TIP (telecom infra project) and OIP (Originating Identification Presentation) cannot be provided to the M2M user. The MCA service is not set in the MMTel-Service-Extra XML, and international roaming may be blocked from the home location register (HLR) associated with the M2M number. In one example, the IP Multimedia Private Identity (IMPI) may not be defined in the home subscriber station (HSS) of the network. In one embodiment, the M2M device cannot initiate video calls. For example, any incoming video calls can be rejected by either responding with 488 or setting the video port to "0" in the 200 OK of the INVITE.

[0063] In one embodiment, when an M2M device dials any valid number, the CTAS (102) can match the called party number against valid numbers in a database or repository, such as, but not limited to, an M2M data XML. If a valid number is found in the database, the CTAS (102) can provide call routing treatment as if the call was initiated from a 10-digit VoLTE number.

[0064] In one embodiment, the CTAS (102) can exclusively enable or disable the call completion rate (CCR) of the M2M number based on a predefined set of instructions. The M2M number indication may further be added to the charging data record (CDR) by the CTAS (102). However, if the M2M device dials any invalid number, the call will be rejected with, but not limited to, SIP error code 484. If the outgoing call is barred, the CTAS (102) can respond with a call rejection announcement, such as 603 Decline with an appropriate announcement. In one example, the call rejection announcement may be mapped with an internal cause code 1054.

[0065] In one embodiment, in the originating leg, when a VoLTE number dials an M2M number associated with an enterprise, the CTAS (102) may perform an MNP query for the dialed M2M number. The MNP query may be responded to with a return of the domain name of the M2M subscriber associated with the M2M number. The LRN may or may not be returned by the MNP query. If the LRN is not provided, the CTAS (102) may not add the Network-Provided-Routing-Information (NPRI) AVP (attribute value pair) to the CCR. An online charging system (OCS) may be used for the called party AVP to apply charging policies, if any.

[0066] In one embodiment, if the dialed M2M number belongs to the second operator set, the MNP query may be skipped and the CTAS (102) may route the call as if it were a PSTN number of the second operator set.

[0067] In one embodiment, if the terminating TAS is operatively coupled to the CTAS (102), it can check whether the R-URI (request uniform resource identifier) ​​or the P-served-user (Previously-Served-User) contains any M2M number. If the M2M number is present in the P-Served-User, the CTAS (102) can check whether the M2M number can receive any incoming calls from the identity present in the information PAI (asserted identity) header. If the identity is not present in the database, M2M data, the CTAS (102) can reject the call with a call rejection announcement, such as 603 Decline, after rendering the announcement. In one example, the call rejection announcement is mapped to an internal cause code 1055. If the user's identity is present in the database, M2M data, the CTAS (102) can route the call as if the dialed number was a 10-digit VoLTE number.

[0068] In one example, the call barring implemented by the Appellate Body (DoT) for VoLTE can also be applied to M2M numbers. The CTAS configuration may be applicable to both VoLTE and M2M users. The M2M user can select a priority service. The P-CSCF can add a priority header to a request signal, such as an INVITE request, originating from the M2M user, and based on this the CTAS (102) can apply a priority service to the M2M user.

[0069] In an exemplary implementation, the system is tested with an operator HSS (home subscriber server). For the operator HSS, the operator HSS can only provide service data that corresponds to the service indication in the M2M data. For other service indications, repository data is available, but service data is not. In that case, the CTAS (102) can take into account default data present in the CTAS. The default data present in the CTAS (102) of the M2M user can be configured as follows: ·MCA (Missed call alert) service is not provisioned The Nat-ss-code value is E · No auxiliary services other than TIP and OIP are provided.

[0070] In one embodiment, the system may be flexible to subsequently provision the appropriate service xml to the M2M user if it is determined that a particular supplementary service needs to be added to the M2M user. In one example, the nomenclature of the service xml should be the same as that currently used for VoLTE devices.

[0071] If the M2M number wants to set up a call forwarding (CF) service either via a facility call or utility interface, the CTAS (102) can be configured to reject the CF. If the M2M user is either not registered or unreachable, the CTAS will not perform any CSRN (CS Domain Routing Number) query, since the M2M number is not allowed to roam in the network.

[0072] In one example, the one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuits, and / or any device that processes data based on operational instructions. In particular, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in the memory 204 of the system 102. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium that may be fetched and executed to create or share data packets via a network service. The memory 204 may include any non-transitory storage device including, for example, a volatile memory such as a RAM, or a non-volatile memory such as an EPROM, a flash memory, and the like.

[0073] In one embodiment, the CTAS 102 may include interface(s) 206. The interface(s) 206 may include various interfaces, such as interfaces for data input and output devices, referred to as I / O devices, storage devices, etc. The interface(s) 206 may facilitate communications for the CTAS 102. The interface(s) 206 may also provide a communications path to one or more components of the system 102. Examples of such components include, but are not limited to, processing engine(s).

[0074] The processing engine(s) 208 may be implemented as a combination of hardware and programming (e.g., programmable instructions) to implement one or more functions of the processing engine(s) 208. In the examples described herein, such a combination of hardware and programming may be implemented in a number of different ways. For example, the programming for the processing engine(s) 208 may be processor-executable instructions stored in a non-transitory machine-readable storage medium, and the hardware of the processing engine(s) 208 may include processing resources (e.g., one or more processors) to execute such instructions. In this example, the machine-readable storage medium may store instructions that, when executed by the processing resources, implement the processing engine(s) 208. In such an example, the system 102 may include a machine-readable storage medium that stores instructions and processing resources for executing the instructions, or the machine-readable storage medium may be separate but accessible to the system 102 and the processing resources. In other examples, the processing engine(s) 208 may be implemented by electronic circuitry.

[0075] The processing engine 208 may include one or more components (as shown in FIG. 2A ), including a session manager (SM) 212, an operations and maintenance (OAM) manager 214, and a troubleshooting manager (TM) 216. The SM 212 may act as a core function delivery module that may be responsible for call processing and service chaining logic execution in the case of a CTAS. The task of processing SIP, HTTP, and Diameter messages belongs to the SM 212. The OAM manager 214 may be responsible for managing fault, configuration, and performance aspects of the CTAS / network devices. The OAM manager 214 may provide an operations and maintenance touch point to the system or CTAS 102. The OAM 216 may be integrated with the EMS / OSS over a RESTful interface. The TM 216 may aggregate log and debug information from all the function managers for troubleshooting. The TM 216 may also provide flexibility to generate debug information in a modular, process, or system manner, for example. Various other functions of the components may be possible. In one embodiment, the database ( 210 ) may include data that may be stored or generated as a result of functions performed by any of the components of the processing engine(s) 208 of the system 102 .

[0076] FIG. 2B illustrates an exemplary representation of a CTAS server according to an embodiment of the present disclosure. As illustrated in FIG. 2C, the CTAS server is a cluster-based solution and can be hosted on one or more servers. Each server has at least four logical interfaces, such as Bond0 (252), Bond1 (254), Bond2 (256), and Bond3 (258), where each Bond is two Ethernet ports logically paired to achieve link-level redundancy. In one example, the Bond0 (252) interface may be used by at least eight blades for internal and database communication. The Bond1 (254) interface can be used by SIP applications residing on at least eight servers for SIP signaling. The Bond2 (256) interface can be used for diameter communication by applications residing on Blade 3 and beyond, such as Blade 3 through Blade 8, while the Bond3 interface can be used for communication with an Element Management System (EMS). In another example, a 10G optical NIC card (262) is used for Bond0 (252), Bond1 (254), and Bond2 (256), and a 1G electrical NIC card (260) is used for Bond3 (258).

[0077] The CTAS can support both IPv4 and IPv6 protocols, the Bond2 (256) and Bond3 (258) interfaces listen on either IPv6 or IPv4 at a given time, and the Bond1 interface listens on IPv4 and IPv6 simultaneously. The Bond0 (252) interface is not used for any external communication and only supports IPv4.

[0078] In one example, the M2M xml information is given as follows: <m2m-data> <voice-data> <incoming-allowed-number>+917012140255,+188228822880,+914957961002,+919872000005< / Incoming-Allowed Number> <outgoing-allowed-number>+917012140255,+188228822880,+914957961002,+919872000005< / Outgoing-Allowed Number> <voice-data> <sms-data> <incoming-allowed-number>+917012140255,+188228822880,+914957961002,+919872000005< / Incoming-Allowed Number> <outgoing-allowed-number>+917012140255,+188228822880,+914957961002,+919872000005< / Outgoing-Allowed Number> <sms-data> <m2m-data>

[0079] The xml information indicates that the user identity defined in the XML information can include international numbers, mobile numbers of other operators, and fixed line numbers of the first operator and second operator set.

[0080] FIG. 3 illustrates an example representation of a flow diagram for facilitating machine to machine (M2M) communication in a network associated with an entity, in accordance with one embodiment of the present disclosure.

[0081] As shown, in one aspect, a method (300) for routing and processing a level 1 (L1) number may include, at 302, receiving, by at least one converge telephony application server (CTAS) 102, one or more predefined request signals from a network device having a predefined M2M number. The CTAS 102 may communicate with one or more network devices associated with the network and a centralized database. In one example, one or more CTAS instances may be deployed in a super core of a network architecture. Each CTAS instance may be dedicated to traffic processing for a given circle. Furthermore, multiple CTAS clusters may be used to serve traffic for a single circle, and each circle may have its own CDL module.

[0082] The method further includes, at 304, identifying, by the CTAS, based on a predetermined set of instructions, whether the given M2M number belongs to a set of unique numbers, where only the set of unique numbers utilize multiple services related to M2M communication. In one embodiment, the CTAS (102) may be configured to store a set of M2M numbers (referred to herein simply as M2M numbers) that may be authorized to initiate and receive calls between at least four endpoints of at least two circles, such as Circle A or Party A and Circle B or Party B.

[0083] Further, the method may include, at 306, invoking, by the CTAS, a call leg to initiate communication with each of the multiple services based on the identification. In one embodiment, in the originating leg, if the VoLTE number dials an M2M number associated with the enterprise, the CTAS (102) may perform an MNP query for the dialed M2M number. The MNP query may be responded to with a return of the domain name of the M2M subscriber associated with the M2M number. The LRN may or may not be returned by the MNP query. If the LRN is not provided, the CTAS (102) may not add an NPRI (Network-Provided-Routing-Information) AVP (attribute value pair) to the CCR. An OCS (online charging system) may be used for the called party AVP to apply charging policies, if any.

[0084] Further, the method may include, at 308, establishing, by the centralized server, simultaneous communication between the network device and multiple services based on the invoked call leg.

[0085] FIG. 4 illustrates an exemplary computer system in which or by which an embodiment of the present disclosure may be utilized, according to an embodiment of the present disclosure. As illustrated in FIG. 4, computer system 400 may include an external storage device 410, a bus 420, a main memory 430, a read-only memory 440, a mass storage device 450, a communication port 460, and a processor 470. Those skilled in the art will recognize that a computer system may include more than one processor and communication port. Processor 470 may include various modules associated with an embodiment of the present invention. Communication port 460 may be an RS-232 port for use with a modem-based dial-up connection, a 10 / 100 Ethernet port, a gigabit or 10 gigabit port using copper or fiber, a serial port, a parallel port, or any other existing or future port. Communication port 460 may be selected depending on the network, such as a local area network (LAN), a wide area network (WAN), or any network to which the computer system is connected. Memory 430 may be a Random Access Memory (RAM) or any other dynamic storage device commonly known in the art. Read-only memory 440 may be any static storage device(s). Mass storage 450 may be any current or future mass storage solution that can be used to store information and / or instructions.

[0086] The bus 420 communicatively couples the processor(s) 470 with other memory, storage, and communication blocks.

[0087] Optionally, operator and management interfaces such as a display, keyboard, and cursor control devices may also be coupled to bus 420 to support direct operator interaction with the computer system. Other operator and management interfaces may be provided through a network connection connected through communications port 460. The above components are intended only to illustrate various possibilities. The foregoing exemplary computer system is not intended to limit the scope of the present disclosure.

[0088] Thus, the present disclosure provides a technical solution for facilitating effective and parallel routing and processing of M2M numbers to provide efficient M2M communications.Several other advantages may be realized.

[0089] Although the embodiments herein are described with respect to a network device or a CTAS, it should be understood that the proposed systems and methods may be implemented in any computing device or external device without departing from the scope of the present invention.

[0090] Although considerable emphasis has been placed herein on the preferred embodiment, it should be understood that many embodiments may be made and many changes may be made in the preferred embodiment without departing from the principles of the invention. These and other changes in the preferred embodiment of the invention will be apparent to those skilled in the art from the disclosure herein, and it should be clearly understood that the foregoing description is to be taken merely as illustrative and not limiting of the invention.

[0091] Portions of the disclosure of this patent document contain material that is subject to intellectual property rights, such as, but not limited to, copyright, designs, trademarks, IC layout designs, and / or trade dress protection, owned by Jio Platforms Limited (JPL) or its affiliates (hereinafter referred to as the Owner). The Owner has no objection to the complete reproduction by anyone of the patent document or patent disclosure as it appears in the Patent and Trademark Office files and records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the Owner. This patent document includes systems and methods defined in 3GPP® Technical Specifications (TS).

[0092] Advantages of the present disclosure The present disclosure provides systems and methods that facilitate efficient, parallel, and improved communication between two or more machines.

[0093] The present disclosure provides systems and methods that allow machines to initiate and receive calls.

[0094] An advantage of the present invention is that the disclosed method and system provides cost-effective communications. < / sms-data> < / sms-data> < / voice-data> < / voice-data> < / m2m-data> < / msisdn> < / cc>

Claims

1. 1. A system for facilitating machine to machine (M2M) communications of entities in a network, comprising: at least one converge telephony application server (CTAS) in communication with one or more network devices associated with the network and with a centralized database; The at least one CTAS is operably coupled to a processor, the processor is coupled to a memory, the memory stores instructions, and upon execution of the instructions, the processor causes the at least one CTAS to: receiving one or more predefined request signals from a network device of the one or more network devices having a predefined M2M number; identifying whether the given M2M number belongs to a set of unique numbers based on a set of predefined instructions, where only the set of unique numbers utilize a plurality of services related to the M2M communication; invoking a call leg to initiate communication with each of the plurality of services based on the identification; The system establishes simultaneous communications between the network device and the plurality of services based on the invoked call leg.

2. The system of claim 1 , wherein the at least one CTAS is configured to capture call services at a first database and message services at a second database during the invoked call leg.

3. 2. The system of claim 1, wherein the predefined M2M number has a predefined length, the predefined length including a Mobile Station International Subscriber Directory Number (MSISDN) Identification (ID) and a respective country code.

4. 2. The system of claim 1, wherein the set of unique numbers is stored in the centralized database, each number in the set of unique numbers is associated with a unique user identification (ID), and the set of unique numbers is given authority for incoming and outgoing calls.

5. 2. The system of claim 1, wherein the set of unique numbers is stored in a predefined format including an international identification (ID), a mobile number, and a fixed line number.

6. 2. The system of claim 1, wherein said centralized database includes predetermined identity numbers associated with predetermined services of said set of unique numbers.

7. 7. The system of claim 6, wherein if an identity is not defined in a given service, the M2M number is allowed to access the given service and incoming calls to the M2M number from any number are allowed.

8. The system of claim 1 , wherein the predefined M2M number has a predefined registration and call flow process.

9. The system of claim 1 , wherein a predetermined caller ring back tone (CRBT) service is applicable to the predetermined M2M number.

10. The system of claim 1 , wherein one or more predefined services flag a predefined instance related to the one or more predefined services as not being able to be associated with the predefined M2M number.

11. The system of claim 1 , wherein roaming facilities are not available for the given M2M number in any network.

12. 2. The system of claim 1, wherein when the network device having the given M2M number dials any valid number, the at least one CTAS checks the called party number in the centralized database, and if the valid number is found in the centralized database, the at least one CTAS provides call routing processing.

13. The system of claim 1 , wherein if the network device having the given M2M number dials any invalid number, the call is rejected with an error code.

14. The system of claim 1 , wherein if an outgoing call is barred for the predefined M2M number, the at least one CTAS responds with a decline with a predefined announcement, the predefined announcement being mapped with a predefined internal cause code.

15. 2. The system of claim 1, wherein when the network device associated with the entity dials the given M2M number on an outgoing leg, the at least one CTAS queries a mobile number portability (MNP) of the dialed M2M number.

16. 16. The system of claim 15, wherein the query to the MNP returns a domain name of the M2M subscriber, and if a location routing number (LRN) is not returned by the MNP, the at least one CTAS does not provide a Network-Provided-Routing-Information (NPRI) to the centralized database.

17. The system of claim 15, wherein if the given M2M number belongs to a second entity, the query to the MNP is skipped and the at least one CTAS routes the call to the given service.

18. The system of claim 1 , wherein a predetermined priority service is available to the one or more network devices having an M2M number.

19. The system of claim 15, wherein the at least one CTAS does not perform a CSRN (CS Domain Routing Number) query if the M2M user is unregistered or unreachable.

20. 1. A method for facilitating machine to machine (M2M) communications in a network associated with an entity, comprising: receiving, by at least one converge telephony application server (CTAS), one or more predefined request signals from a network device having a predefined M2M number, the at least one CTAS in communication with one or more network devices associated with the network and a centralized database; identifying, by the at least one CTAS, whether the given M2M number belongs to a group of unique numbers based on a predefined set of instructions, where only the group of unique numbers utilizes a plurality of services related to the M2M communication; invoking, by the at least one CTAS, a call leg to initiate communication with each of the plurality of services based on the identification; establishing, by the at least one CTAS, simultaneous communication between the network device and the plurality of services based on the invoked call leg; The method comprising:

21. 21. The method of claim 20, comprising capturing, by the at least one CTAS, a call service at a first database and a message service at a second database during the invoked call leg.

22. 21. The method of claim 20, wherein the predefined M2M number has a predefined length, the predefined length including a Mobile Station International Subscriber Directory Number (MSISDN) Identification (ID) and a respective country code.

23. 21. The method of claim 20, wherein the set of unique numbers is stored in the centralized database, and each number in the set of unique numbers is associated with a unique user identification (ID), and the set of unique numbers is authorized for incoming and outgoing calls.

24. 21. The method of claim 20, wherein the set of unique numbers is stored in a predefined format including an international identification (ID), a mobile number, and a fixed line number.

25. 21. The method of claim 20, wherein the centralized database includes predefined identity numbers associated with predefined services of the set of unique numbers.

26. 26. The method of claim 25, wherein if no identity is defined in the given service, the given M2M number is allowed to access the given service and incoming calls to the given M2M number from any number are allowed.

27. The method of claim 20 , wherein the predefined M2M number has a predefined registration and call flow process.

28. The method of claim 20, wherein a predetermined caller ring back tone (CRBT) service is applicable to the predetermined M2M number.

29. 21. The method of claim 20, wherein one or more predefined services flag a predefined instance related to the one or more predefined services as not being able to be associated with the predefined M2M number.

30. 21. The method of claim 20, wherein roaming facilities are not available for the given M2M number in any network.

31. 21. The method of claim 20, wherein if the network device having the given M2M number dials any valid number, the method includes checking, by the at least one CTAS, a called party number in the centralized database, and if the valid number is found in the centralized database, the method includes providing, by the at least one CTAS, call routing handling.

32. 21. The method of claim 20, wherein if the network device having the given M2M number dials any invalid number, the method comprises rejecting, by the at least one CTAS, the call with an error code.

33. 21. The method of claim 20, wherein if outgoing calls are barred for the predefined M2M number, the method comprises responding, by the at least one CTAS, with a decline with a predefined announcement, the predefined announcement being mapped with a predefined internal cause code.

34. 21. The method of claim 20, wherein when the network device associated with the entity dials the predefined M2M number on an originating leg, the method includes querying, by the at least one CTAS, a Mobile number portability (MNP) number of the dialed M2M number.

35. 35. The method of claim 34, wherein the query to the MNP returns a domain name of the M2M subscriber and if a location routing number (LRN) is not returned by the MNP, the method comprises discarding, by the at least one CTAS, a Network-Provided-Routing-Information (NPRI) in the centralized database.

36. 35. The method of claim 34, wherein if the predetermined M2M number belongs to a second entity, the query to the MNP is skipped, and the method includes routing the call by the at least one CTAS to the predetermined service.

37. The method of claim 20 , wherein a predetermined priority service is available to the one or more network devices having an M2M number.

38. 35. The method of claim 34, comprising ignoring a CSRN query by the at least one CTAS if the M2M user is not registered or is unreachable.

39. A user equipment (UE) (108) communicatively coupled to at least one converge telephony application server (CTAS) (102), comprising: The bond of the CTAS (102) is receiving a connection request from the UE (108) to dial a machine to machine (M2M) number; sending an acknowledgment of said connection request to said CTAS (102); transmitting a plurality of signals in response to the connection request; The UE comprising:

40. A non-transitory computer-readable medium containing machine-executable instructions, comprising: The machine executable instructions include: receiving one or more predefined request signals from a network device having a predefined machine to machine (M2M) number; Identifying whether the given M2M number belongs to a set of unique numbers based on a set of predefined instructions, and only the set of unique numbers utilizing a plurality of services related to M2M communications; invoking a call leg to initiate communication with each of the plurality of services based on the identification; establishing simultaneous communications between the network device and the plurality of services based on the invoked call legs; The non-transitory computer-readable medium is executable by a processor to:

Images