Service bearer method, system and device based on converged network element and storage medium

Abstract

The application discloses a service bearing method, system and device based on a fusion network element, a storage medium and construction of the fusion network element, and access of user services of 4G and 5G to the fusion network element; through the fusion network element, a user type of a target user currently processed is identified according to a 5GS IWK ind field in a session creation S5 message; and a service flow of the target user is borne and processed according to the user type; wherein the user type includes HSS 4G users of an Internet of Things inventory and newly added UDM 4G users. The method maintains an existing two-level architecture of a provincial network and a special network node, adopts a 5G fusion network element to bear Internet of Things 4G services, gradually migrates services to a 5G network element in the provincial network, fuses on demand, flexibly matches various 2B service development requirements, and naturally has a provincial network shunting capability, thereby relieving bearing network pressure. The application can be widely applied in the field of communication technology.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to service carrying methods, systems, devices and storage media based on converged network elements. Background Technology

[0002] Currently, the mainstream technologies for the Internet of Things (IoT) are 4G / 5G, which can be further divided into non-NB-IoT services and NB-IoT services based on the wireless standard. The access network relies on 31 provinces for access, employing a two-tier network architecture with 4G / 5G coexisting to meet centralized control and multi-point distributed access requirements. The provincial access network and dedicated network central nodes are connected through a public bearer network. This centralized approach meets the requirements for unified and intensive management of user data and service policies. Other network elements fully reuse the 5G network resources of the 31 provinces, ensuring optimal service experience and saving investment.

[0003] In related technologies, the centralized nodes of private networks need continuous expansion. Considering that 4G network elements will be upgraded to 5G network elements, and the limited lifespan of 4G networks, and given the maturity of the 5G IoT terminal industry chain, 4G IoT services will be gradually migrated to 5G networks by replacing terminals. As development needs increase, 4G IoT will need to gradually evolve into 5G network elements. 5G network elements carrying 4G IoT services may encounter situations where both 4G and 5G users are simultaneously supported, raising issues regarding control strategies for existing and new users.

[0004] In summary, the problems with the relevant technologies urgently need to be addressed. Summary of the Invention

[0005] The purpose of this application is to at least partially solve one of the technical problems existing in the related art.

[0006] Therefore, one objective of the embodiments of this application is to provide a service carrying method, system, device, and storage medium based on converged network elements.

[0007] To achieve the above-mentioned technical objectives, the technical solutions adopted in the embodiments of this application include:

[0008] On the one hand, embodiments of this application provide a service carrying method based on converged network elements, the method comprising:

[0009] Construct a converged network element and connect 4G and 5G user services to the converged network element;

[0010] The user type of the target user being processed is identified by the fused network element based on the 5GS IWK ind field in the S5 message created during the session.

[0011] Based on the user type, a business process for processing the target user is implemented;

[0012] The user types include existing HSS 4G users and newly added UDM 4G users.

[0013] In addition, the service carrying method based on converged network elements according to the above embodiments of this application may also have the following additional technical features:

[0014] Furthermore, in one embodiment of this application, the step of accessing 4G and 5G user services to the converged network element includes:

[0015] The address information of the converged network element is added to the access point name or access point operator identifier of the Internet of Things through the Domain Name System;

[0016] The mobility management entity connects user services to the converged network element based on the data network name and tracking area code.

[0017] Furthermore, in one embodiment of this application, identifying the user type of the target user currently being processed based on the 5GS IWK ind field in the session creation S5 message includes:

[0018] If the 5GS IWK ind field is 1, the user type of the target user is determined to be an HSS 4G user;

[0019] If the 5GS IWK ind field is 0 or not carried, the user type of the target user is determined to be a UDM4G user.

[0020] Furthermore, in one embodiment of this application, the step of carrying out the business process for processing the target user according to the user type includes:

[0021] When the user type of the target user is determined to be an HSS 4G user, a 4G APN is configured on the converged network element;

[0022] Enable the IWK switch and provide the Gx interface to connect with the diameter routing proxy;

[0023] Obtain user PCC policies from IoT policy and billing rules functions, and use the N40 interface for billing.

[0024] Furthermore, in one embodiment of this application, the step of carrying out the business process for processing the target user according to the user type includes:

[0025] When the target user is determined to be a UDM 4G user, the service is activated and the 5G function is deactivated in accordance with the 5G product model.

[0026] The PCF control policy is received via the N7 interface, and billing is performed via the N40 interface.

[0027] Furthermore, in one embodiment of this application, the service process for handling the target user includes:

[0028] The attachment request information of the target user is received through the mobility management entity;

[0029] The authentication process for the target user is performed based on the mobility management entity, and a user session is initiated.

[0030] On the other hand, embodiments of this application provide a service carrying system based on converged network elements, the system comprising:

[0031] An access unit is used to construct a converged network element and to access 4G and 5G user services to the converged network element.

[0032] The identification unit is used to identify the user type of the target user currently being processed based on the 5GS IWK ind field in the S5 message created in the session, through the converged network element.

[0033] The processing unit is used to carry out the business process of processing the target user according to the user type;

[0034] The user types include existing HSS 4G users and newly added UDM 4G users.

[0035] Furthermore, in one embodiment of this application, the access unit is specifically used for:

[0036] The address information of the converged network element is added to the access point name or access point operator identifier of the Internet of Things through the Domain Name System;

[0037] The mobility management entity connects user services to the converged network element based on the data network name and tracking area code.

[0038] On the other hand, embodiments of this application provide an electronic device, including:

[0039] At least one processor;

[0040] At least one memory for storing at least one program;

[0041] When the at least one program is executed by the at least one processor, the at least one processor implements the above-described service carrying method based on converged network elements.

[0042] On the other hand, embodiments of this application also provide a computer-readable storage medium storing a processor-executable program, which, when executed by a processor, is used to implement the above-described service carrying method based on converged network elements.

[0043] The advantages and beneficial effects of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application:

[0044] The service carrying method, system, device, and storage medium based on converged network elements disclosed in this application construct converged network elements and access 4G and 5G user services to these converged network elements. Through these converged network elements, the user type of the target user being processed is identified based on the 5GS IWK ind field in the session creation S5 message. Based on the user type, the service process for processing the target user is carried. The user types include existing HSS 4G users and newly added UDM 4G users. This method maintains the existing two-tier architecture of provincial and private network nodes, uses 5G converged network elements to carry IoT 4G services, gradually migrates services to provincial 5G network elements, integrates services on demand, flexibly matches various 2B service development needs, and naturally possesses provincial offloading capabilities, alleviating pressure on the transport network. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the following description is provided with accompanying drawings of the relevant technical solutions in the embodiments of this application or the prior art. It should be understood that the accompanying drawings described below are only for the purpose of clearly illustrating some embodiments of the technical solutions of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0046] Figure 1 This is a schematic diagram of the implementation environment for a service carrying method based on converged network elements provided in the embodiments of this application;

[0047] Figure 2 This is a flowchart illustrating a service carrying method based on converged network elements provided in the embodiments of this application;

[0048] Figure 3 This is a schematic diagram illustrating a process for accessing 4G and 5G user services to a converged network element, as provided in an embodiment of this application.

[0049] Figure 4 This is a schematic diagram of a process for identifying the user type of the target user currently being processed, provided in an embodiment of this application.

[0050] Figure 5 This is a flowchart illustrating a business process for handling target users, as provided in an embodiment of this application.

[0051] Figure 6This is a flowchart illustrating another business process for handling target users provided in this application embodiment;

[0052] Figure 7 This is a schematic diagram of HSS 4G user service processing provided in an embodiment of this application;

[0053] Figure 8 This is a schematic diagram of a UDM 4G user service processing provided in an embodiment of this application;

[0054] Figure 9 This is a schematic diagram of the structure of a service carrying system based on converged network elements provided in the embodiments of this application;

[0055] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0056] The present application will be further described below with reference to the accompanying drawings and specific embodiments. The described embodiments should not be considered as limitations on the present application, and all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of the present application.

[0057] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0058] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0059] 1) SMF (Session Management Function): The session management function is responsible for managing and controlling user sessions, including the establishment, maintenance and release of user sessions, as well as the allocation and management of user IP addresses and QoS policies.

[0060] 2) UPF (User Plane Function): User plane function, responsible for handling the forwarding and routing of user data, and implementing functions such as packet segmentation, transmission and optimization.

[0061] 3) PGW-C (PDN Gateway-Control Plane): Data network gateway-control plane, responsible for implementing user session management, network access control and security control, including the establishment, maintenance and release of user sessions, as well as user authentication, access authentication and IP address allocation, etc.

[0062] 4) PCF (Policy Control Function): This function is responsible for implementing and managing network policies, including formulating user policies, exchanging control information, and executing policies.

[0063] 5) PCRF (Policy and Charging Rules Function): This function is responsible for formulating, managing, and enforcing network policies and charging rules, including the formulation of user policies, the formulation of charging rules, and the exchange of policy and charging information.

[0064] 6) UDM (Unified Data Management): Unified data management function, responsible for the management and storage of user data, including the management of user identity, permissions, policies and configuration information.

[0065] 7) HSS (Home Subscriber Server): The home user server is responsible for storing and managing user identity and authentication information, as well as user service configuration and access permissions.

[0066] 8) DNS (Domain Name System): DNS is used to translate domain names (such as www.example.com) into their corresponding IP addresses. In the Internet of Things (IoT), DNS helps devices find the correct network nodes.

[0067] 9) APN (Access Point Name): An APN is an identifier used to provide a device with an access point to a specific network. It allows devices to access specific network services in the Internet of Things (IoT).

[0068] 10) APNOI (APN Operator Identifier): APNOI is an identifier used to identify a specific operator. It is associated with the APN and indicates which operator's network a device can connect to.

[0069] 11) DNN (Data Network Name): DNN is an identifier used to identify the data network to which a device connects in the Internet of Things (IoT). It is associated with the device's APN and indicates the type of network and service to which the device is connected.

[0070] 12) TAC (Tracking Area Code): A TAC is an identifier used to identify a tracking area in a mobile network. It is associated with the location of the device, and the MME uses the TAC to determine the tracking area where the device is located.

[0071] 13) Converged SMF / SAE GWC with S / P integration: This refers to the integration of S-GW (Serving Gateway) and P-GW (PDN Gateway) functions into a converged SMF / SAE GWC in the Internet of Things, enabling a single network element to handle data transmission and control of devices.

[0072] 14) IWK ind (Interworking indication): The converged SMF / GW-C (control plane gateway) creates an S5 message based on the session, and the 5GS interworking ind field is 0, 1, or not carried. When it is 0 or not carried, it is identified as a 5G user and the N7 and N40 interfaces are selected for the user; when it is 1, it is identified as an IoT 4G user and the Gx, Gy, and Ga interfaces are selected for the user.

[0073] 15) Gx Interface: The Gx interface is used in the Internet of Things (IoT) for communication between devices and the PCRF (Policy and Charging Rules Function). It is used to obtain the device's PCC (Policy and Charging Control) policy.

[0074] 16) N40 Interface: The N40 interface is used for communication between the SGW / PGW-C and the billing system. It is used to transmit equipment usage information to the billing system for billing purposes.

[0075] 17) The MME, or Mobility Management Entity, is a key network element in LTE (Long Term Evolution) networks. The MME is responsible for mobility management functions, including device authentication, location management, session management, and security control. It communicates with other network elements such as the SGW (Serving Gateway) and HSS (Home Subscriber Server) and coordinates operations such as mobile device registration, authentication, location updates, session establishment, and release. The MME is also responsible for ensuring seamless connectivity and smooth handover when mobile devices switch from one base station (eNodeB) to another. Therefore, the MME plays a crucial control and management role in LTE networks.

[0076] Reference Figure 1 , Figure 1 This illustration shows a schematic diagram of a 4 / 5G converged network provided in an embodiment of this application. Currently, the mainstream IoT technology is 4G / 5G, which can be further divided into non-NB-IoT services and NB-IoT services based on the wireless standard. The access network relies on 31 provinces for access, employing a two-tier network architecture with 4G / 5G coexisting. This satisfies centralized control and multi-point distributed access. The provincial access network and dedicated network centralized nodes are connected through a public bearer network, enabling data transmission and interaction between different regions and providing broader service coverage. Because of this intensive approach, it meets the requirements for unified and intensive management of user data and service strategies. Other network elements fully reuse the 5G GC resources of the 31 provinces, ensuring the best service experience and saving investment.

[0077] In practical applications of related technologies, the following problems have been found:

[0078] (1) The issue of gradually upgrading 4G IoT services to 5G. Private network centralized nodes need to be continuously expanded, and considering that 4G terminals will be upgraded to 5G terminals, the number of years that 4G networks will remain in service is limited. In combination with the maturity of the 5G IoT terminal industry chain, 4G IoT services will be gradually migrated to 5G networks by replacing terminals; with the development needs, 4G IoT needs to be gradually upgraded to 5G devices.

[0079] (2) The problem of 5G network elements simultaneously carrying 4G and 5G services. When 5G network elements carry IoT 4G services, there is a problem of simultaneously carrying 4G / 5G users, as well as control strategies for existing users and new users.

[0080] (3) High load on the bearer network. The public bearer network has a high load. The access network relies on 31 provinces for access, that is, it adopts a two-level network architecture with 4G / 5G coexisting. The provincial access network and the centralized nodes of the private network are connected through the public bearer network. The user plane will increase the pressure on the public bearer network at the centralized nodes.

[0081] In view of this, this application provides a service carrying method based on converged network elements. This method maintains the existing two-level architecture of provincial and private network nodes, uses 5G converged network elements to carry IoT 4G services, gradually migrates services to 5G network elements within the province, integrates on demand, flexibly matches the development needs of various 2B services, and naturally has the ability to offload traffic within the province, thus alleviating the pressure on the bearer network.

[0082] Below, in conjunction with the aforementioned implementation environment, a service carrying method based on converged network elements provided in this application embodiment will be introduced and explained.

[0083] Please refer to Figure 2 , Figure 2 This is a schematic diagram of a service carrying method based on converged network elements provided in an embodiment of this application. The service carrying method based on converged network elements includes, but is not limited to:

[0084] Step 210: Construct a converged network element and access 4G and 5G user services to the converged network element;

[0085] Step 220: Using the converged network element, identify the user type of the target user being processed based on the 5GS IWK ind field in the S5 message created during the session.

[0086] Step 230: Based on the user type, implement the business process for processing the target user;

[0087] The user types include existing HSS 4G users and newly added UDM 4G users.

[0088] In this application embodiment, a service carrying method based on converged network elements is provided. This method maintains the existing two-level architecture of provincial and private network nodes, uses 5G converged network elements to carry IoT 4G services, gradually migrates services to 5G network elements within the province, integrates on demand, flexibly matches the development needs of various 2B services, and naturally has the ability to offload traffic within the province, thus alleviating the pressure on the bearer network.

[0089] Specifically, in this embodiment, a converged network element, such as a 5G 2B SMF / UPF, can be constructed. The SMF (Session Management Function) is responsible for managing and controlling user sessions, including establishing, maintaining, and releasing user sessions, as well as allocating and managing user IP addresses and QoS policies. The UPF (User Plane Function) is responsible for handling user data forwarding and routing, implementing functions such as packet segmentation, transmission, and optimization. Then, the 5G converged network element SMF / UPF can be used to carry 4G and 5G user services for the Internet of Things (IoT). It should be noted that the types of converged network elements in this embodiment can be various, and this application does not impose any limitations on this.

[0090] Please refer to Figure 3 In some embodiments, accessing 4G and 5G user services to the converged network element includes:

[0091] The address information of the converged network element is added to the access point name or access point operator identifier of the Internet of Things through the Domain Name System;

[0092] The mobility management entity connects user services to the converged network element based on the data network name and tracking area code.

[0093] In this embodiment, the address information of the converged network element SMF / PGW-C corresponding to the APN (Access Point Name) and APNOI (Access Point Name) of the Internet of Things can be added through DNS (Domain Name System). This allows the MME (Mobility Management Entity) to select the S / P integrated converged network element SMF / SAE GWC based on the DNN (Data Network Name) and TAC (Tracking Area Code), enabling the user to access the converged 2B SMF / UPF.

[0094] In this embodiment of the application, the converged network element SMF / GW-C can identify existing HSS 4G users or newly added UDM 5G users based on whether the 5GS IWK ind field in the S5 message created in the session is 0, 1, or not carried.

[0095] Specifically, please refer to Figure 4 In some embodiments, identifying the user type of the target user currently being processed based on the 5GS IWK ind field in the S5 message created during the session includes:

[0096] If the 5GS IWK ind field is 1, the user type of the target user is determined to be an HSS 4G user;

[0097] If the 5GS IWK ind field is 0 or not carried, the user type of the target user is determined to be a UDM4G user.

[0098] In this embodiment of the application, if the 5GS IWK ind field in the session creation S5 message is determined to be 1, the user type of the target user can be determined to be an HSS 4G user; if the 5GS IWK ind field in the session creation S5 message is determined to be 0 or not carried, the user type of the target user can be determined to be a UDM 4G user.

[0099] Specifically, please refer to Figure 5 In some embodiments, the process of handling the target user based on the user type includes:

[0100] When the user type of the target user is determined to be an HSS 4G user, a 4G APN is configured on the converged network element;

[0101] Enable the IWK switch and provide the Gx interface to connect with the diameter routing proxy;

[0102] Obtain user PCC policies from IoT policy and billing rules functions, and use the N40 interface for billing.

[0103] In this embodiment of the application, for existing HSS 4G users, the bearer method is as follows: First, after the HSS number is subscribed, the converged network element SMF / UPF is compatible with PGW-C / PGW-U. A 4G APN can be configured on the SMF, the IWK switch can be turned on, and the Gx interface can be provided to interface with DRA (Diameter Routing Agent). The user PCC policy can be obtained from the existing IoT PCRF (Policy and Charging Rules Function). The converged network element acts as SGW / PGW-C, and the billing can use the N40 interface.

[0104] Specifically, please refer to Figure 6 In some embodiments, the process of handling the target user based on the user type includes:

[0105] When the target user is determined to be a UDM 4G user, the service is activated and the 5G function is deactivated in accordance with the 5G product model.

[0106] The PCF control policy is received via the N7 interface, and billing is performed via the N40 interface.

[0107] In this embodiment of the application, for UDM 4G users, the newly added 4G user number segment is opened in UDM and activated according to the 5G product plan, but the 5G function is disabled. The PCF (Policy Control Function) issues policies through the N7 interface. The converged network element SMF / UPF is compatible with PGW-C / PGW-U. 5G LBO DNN can be configured on the SMF, the IWK switch is turned off, and the PCF control policy is received through the N7 interface. Billing can use the N40 interface.

[0108] In this embodiment of the application, 5G services are also carried through the converged network element SMF / UPF. 5G services use dedicated customized DNN+ slices, the IWK switch is turned off by default, and the PCC policy is issued through the N7 interface.

[0109] It should be noted that in this embodiment, the converged network element can be built within the province and is not located at the IoT aggregation node. Simple high-traffic services access from the provincial SMF / UPF and connect directly to the public network, minimizing the CN2 transmission requirements from the provincial network to the IoT aggregation network node, providing intra-provincial traffic offloading capability, and alleviating the pressure on the bearer network.

[0110] In this embodiment, when the 4G equipment of the private network node ages and is phased out, the data plane 4G / 5G is converged, and the billing and PCC policies are unified through a single interface. The DNS adds converged SMF / PGW-C addresses corresponding to APN and APN OI. The MME selects the converged SMF / SAE GW-C based on the DNN and TA, and preferentially uses the S / P unified network element. The 5G PCF is upgraded to a converged PCF / PCRF, providing unified PCC policies for both 4G and 5G users. The 5G UDM is upgraded to a converged UDM / HSS, providing unified number allocation / subscription services for both 4G and 5G users.

[0111] In some embodiments, the business process carrying out the processing of the target user includes:

[0112] The attachment request information of the target user is received through the mobility management entity;

[0113] The authentication process for the target user is performed based on the mobility management entity, and a user session is initiated.

[0114] The following describes and explains the service carrying method based on converged network elements provided in the embodiments of this application, with reference to specific examples.

[0115] Reference Figure 7 , Figure 7This illustration shows a schematic diagram of HSS 4G user service processing provided in an embodiment of this application. After using the 5G converged network element SMF / UPF to carry HSS / PCRF account opening user services, the specific access process is as follows:

[0116] (1) When the UE powers on, it initiates an attach request and sends an Attach Request (IMSI) message to the MME. That is, after the UE powers on, it sends an attach request message to the MME (Mobility Management Entity), which contains the International Mobile Subscriber Identity (IMSI).

[0117] (2) After receiving the Attach Request message, the MME sends an Authentication Information Request (IMSI) to the HSS (Home Subscriber Server). The HSS responds with an Authentication Information Answer message, carrying the EPS (Extended Packet System) security vector.

[0118] (3) The MME initiates the authentication and security process;

[0119] (4) The MME sends an Update Location Request message to the HSS to update the location, including the current RAT; the HSS responds with an Update Location Answer message, which contains the subscription data;

[0120] (5) Based on the DNN and TAC, the MME selects the S / P integrated converged network element SMF / SGW-C and triggers the establishment of the offloaded user session;

[0121] (6) After the update is successful, the MME sends a Create Session Request message to the converged network element SMF / SGW-C to request the establishment of a default bearer;

[0122] (7) The converged network element SMF / SGW-C sends a Create Session Request message to the converged network element SMF / PGW-C;

[0123] (8) Based on the 5GS interworking ind field being 1 in the S5 message created during the session, the user is identified as an IoT HSS / PCRF user. The Gx, Gy, and Ga interfaces are selected for the IoT HSS 4G user.

[0124] (9) The converged network element PGW-C sends a CCR-I message to PCRF to request the establishment of an IP CAN session;

[0125] (10) The PCRF responds to the CCA-I message and sends the corresponding policy to the user;

[0126] (11) The converged network element PGW-C responds with a Create Session Response message to the converged network element SMF / SGW-C, and then the SGW responds with a Create Session Response to the MME;

[0127] (12) The MME sends an Initial Context Setup Request to the eNodeB, which carries an AttachAccept message containing an Activate Default EPS Bearer Context Request message, requesting the establishment of a default bearer;

[0128] (13) The UE returns Attach Complete, and the eNodeB returns the Initial Context Setup Response message;

[0129] (14) The MME sends a Modify Bearer Request message to the converged network element SMF / SGW-C to update the eNodeB address and TEID, and the SGW responds with a success message.

[0130] Reference Figure 8 , Figure 8 This illustration shows a schematic diagram of UDM 4G user service processing provided in an embodiment of this application. After using the 5G converged network element SMF / UPF to carry UDM / PCF account opening user services, the specific access process is as follows:

[0131] (1) The UE initiates an attach process upon power-on and sends an Attach Request (IMSI) message to the MME;

[0132] (2) After receiving the Attach Request message, the MME sends an Authentication Information Request (IMSI) to the HSS (Home Subscriber Server). The HSS responds with an Authentication Information Answer message, carrying the EPS security vector.

[0133] (3) The MME initiates the authentication and security process;

[0134] (4) The MME sends an Update Location Request message to the UDM to update the location, including the current RAT; the UDM responds with an Update Location Answer message, which contains the subscription data;

[0135] (5) Based on the DNN and TAC, the MME selects the S / P integrated converged network element SMF / SGW-C and triggers the establishment of the offloaded user session;

[0136] (6) After the update is successful, the MME sends a Create Session Request message to the converged network element SMF / SGW-C to request the establishment of a default bearer;

[0137] (7) The converged network element SMF / SGW-C sends a Create Session Request message to the converged network element SMF / PGW-C;

[0138] (8) If the 5GS interworking ind field in the S5 message created in the session is 0 or not carried, it is identified as an IoT UDM / PCF user, and the N7 and N40 interfaces are selected for the UDM 4G user;

[0139] (9) The converged network element SMF sends a CCR-I message to the PCF to request the establishment of an IP CAN session;

[0140] (10) The PCF responds to the CCA-I message to the converged network element SMF and sends the corresponding policy to the user;

[0141] (11) The converged network element SMF responds with a Create Session Response message to the converged network element SMF / SGW-C, and then the SGW responds with a Create Session Response to the MME;

[0142] (12) The MME sends an Initial Context Setup Request to the eNodeB, which carries an AttachAccept message containing an Activate Default EPS Bearer Context Request message, requesting the establishment of a default bearer;

[0143] (13) The UE returns Attach Complete, and the eNodeB returns the Initial Context Setup Response message;

[0144] (14) The MME sends a Modify Bearer Request message to the converged network element SMF / SGW-C to update the eNodeB address and TEID, and the SGW responds with a success message.

[0145] It is understood that the service carrying method based on converged network elements provided in this application embodiment maintains the existing two-level architecture of provincial and private network nodes, uses 5G converged network elements to carry IoT 4G services, gradually migrates services to 5G network elements within the province, integrates on demand, flexibly matches the development needs of various 2B services, and naturally has the ability to offload traffic within the province, thus alleviating the pressure on the bearer network.

[0146] Reference Figure 9 This application also provides a service carrying system based on converged network elements, including:

[0147] Access unit 910 is used to construct a converged network element and to access 4G and 5G user services to the converged network element;

[0148] The identification unit 920 is used to identify the user type of the target user currently being processed based on the 5GS IWK ind field in the session creation S5 message through the converged network element.

[0149] Processing unit 930 is used to carry out the business process of processing the target user according to the user type;

[0150] The user types include existing HSS 4G users and newly added UDM 4G users.

[0151] Furthermore, in one embodiment of this application, the access unit is specifically used for:

[0152] The address information of the converged network element is added to the access point name or access point operator identifier of the Internet of Things through the Domain Name System;

[0153] The mobility management entity connects user services to the converged network element based on the data network name and tracking area code.

[0154] It is understood that the content of the above method embodiments is applicable to this system embodiment. The specific functions implemented in this system embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0155] Reference Figure 10 This application provides an electronic device, including:

[0156] At least one processor 1010;

[0157] At least one memory 1020 is used to store at least one program;

[0158] When at least one program is executed by at least one processor 1010, it enables the at least one processor 1010 to implement a service carrying method based on converged network elements.

[0159] Similarly, the content of the above method embodiments is applicable to the embodiments of this electronic device. The specific functions implemented by the embodiments of this electronic device are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0160] This application embodiment also provides a computer-readable storage medium storing a program executable by a processor 1010, which, when executed by the processor 1010, is used to perform the above-described service carrying method based on converged network elements.

[0161] Similarly, the content of the above method embodiments is applicable to the present computer-readable storage medium embodiments. The specific functions implemented by the present computer-readable storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0162] In some alternative embodiments, the functions / operations mentioned in the block diagrams may not occur in the order shown in the operation diagrams. For example, depending on the functions / operations involved, two consecutively shown blocks may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order. Furthermore, the embodiments presented and described in the flowcharts of this application are provided by way of example to provide a more comprehensive understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed and sub-operations described as part of a larger operation are executed independently.

[0163] Furthermore, although this application is described in the context of functional modules, it should be understood that, unless otherwise stated to the contrary, one or more of the functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding this application. Rather, given the properties, functions, and internal relationships of the various functional modules in the apparatus disclosed herein, the actual implementation of the module will be understood within the scope of conventional technology for an engineer. Therefore, those skilled in the art can implement the application set forth in the claims using ordinary techniques without excessive experimentation. It is also understood that the specific concepts disclosed are merely illustrative and not intended to limit the scope of this application, which is determined by the full scope of the appended claims and their equivalents.

[0164] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0165] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0166] More specific examples of computer-readable media (a non-exhaustive list) include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0167] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0168] In the foregoing description of this specification, the references to terms such as "one embodiment," "another embodiment," or "some embodiments," etc., indicate that a specific feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0169] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

[0170] The above is a detailed description of the preferred embodiments of this application, but this application is not limited to the embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application, and these equivalent modifications or substitutions are all included within the scope defined by the claims of this application.

Claims

1. A service carrying method based on converged network elements, characterized in that, The method includes: Construct a converged network element and connect 4G and 5G user services to the converged network element; The user type of the target user being processed is identified by the converged network element based on the 5GS IWK ind field in the S5 message created during the session. Based on the user type, a business process for processing the target user is implemented; The user types include existing HSS 4G users and newly added UDM 4G users; The step of identifying the user type of the target user currently being processed based on the 5GS IWK ind field in the S5 message created during the session includes: If the 5GS IWK ind field is 1, the user type of the target user is determined to be an HSS 4G user; If the 5GS IWK ind field is 0 or not carried, the user type of the target user is determined to be a UDM 4G user; The business process for handling the target user based on the user type includes: When the target user is determined to be a UDM 4G user, the service is activated and the 5G function is deactivated in accordance with the 5G product model. The PCF control policy is received via the N7 interface, and billing is performed via the N40 interface.

2. The service carrying method based on converged network elements according to claim 1, characterized in that, The process of connecting 4G and 5G user services to the converged network element includes: The address information of the converged network element is added to the access point name or access point operator identifier of the Internet of Things through the Domain Name System; The mobility management entity connects user services to the converged network element based on the data network name and tracking area code.

3. The service carrying method based on converged network elements according to claim 1, characterized in that, The business process for handling the target user based on the user type includes: When the user type of the target user is determined to be an HSS 4G user, a 4G APN is configured on the converged network element; Enable the IWK switch and provide the Gx interface to connect with the diameter routing proxy; Obtain user PCC policies from IoT policy and billing rules functions, and use the N40 interface for billing.

4. The service carrying method based on converged network elements according to claim 1, characterized in that, The business process that carries out the processing of the target user includes: The attachment request information of the target user is received through the mobility management entity; The authentication process for the target user is performed based on the mobility management entity, and a user session is initiated.

5. A service carrying system based on converged network elements, characterized in that, The system includes: An access unit is used to construct a converged network element and to access 4G and 5G user services to the converged network element. The identification unit is used to identify the user type of the target user currently being processed based on the 5GS IWK ind field in the S5 message created in the session, through the converged network element. The processing unit is used to carry out the business process of processing the target user according to the user type; The user types include existing HSS 4G users and newly added UDM 4G users; The step of identifying the user type of the target user currently being processed based on the 5GS IWK ind field in the S5 message created during the session includes: If the 5GS IWK ind field is 1, the user type of the target user is determined to be an HSS 4G user; If the 5GS IWK ind field is 0 or not carried, the user type of the target user is determined to be a UDM 4G user; The business process for handling the target user based on the user type includes: When the target user is determined to be a UDM 4G user, the service is activated and the 5G function is deactivated in accordance with the 5G product model. The PCF control policy is received via the N7 interface, and billing is performed via the N40 interface.

6. A service carrying system based on converged network elements according to claim 5, characterized in that, The access unit is specifically used for: The address information of the converged network element is added to the access point name or access point operator identifier of the Internet of Things through the Domain Name System; The mobility management entity connects user services to the converged network element based on the data network name and tracking area code.

7. An electronic device, characterized in that, include: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements a service carrying method based on converged network elements as described in any one of claims 1-4.

8. A computer-readable storage medium storing a processor-executable program, characterized in that: The processor-executable program, when executed by the processor, is used to implement a service carrying method based on converged network elements as described in any one of claims 1-4.

Images