CN112956241B

CN112956241B - Service request method, electronic equipment and storage medium

Info

Publication number: CN112956241B
Application number: CN201980056157.7A
Authority: CN
Inventors: 刘建华; 许阳; 陈振豪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-09-26
Filing date: 2019-09-26
Publication date: 2023-08-25
Anticipated expiration: 2039-09-26
Also published as: CN112956241A; WO2021056356A1

Abstract

The application discloses a service request method, which comprises the following steps: and the terminal equipment residing in the non-public network establishes connection with a third network element in the second public network through the second network element in the non-public network according to the service information of the service request or the first indication information which is sent by the first network element in the first public network and aims at the service request. The application also discloses another service request method, electronic equipment and a storage medium.

Description

Service request method, electronic equipment and storage medium

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a service request method, an electronic device, and a storage medium.

Background

Part of the services of the terminal equipment need to be implemented in the Public Network, so when the terminal equipment resides in a Non-Public Network (NPN) in the Non-Public Network, the terminal equipment needs to be accessed to the Public Network to implement the corresponding services. And, some services of the terminal device need to be implemented in a specific public network. Therefore, how to make service requests to a public network by terminal devices residing in a non-public network is a problem to be solved.

Disclosure of Invention

In order to solve the technical problems, embodiments of the present application provide a service request method, an electronic device, and a storage medium, which can implement service request from a terminal device residing in a non-public network to a public network.

In a first aspect, an embodiment of the present application provides a service request method, including: and the terminal equipment residing in the non-public network establishes connection with a third network element in the second public network through the second network element in the non-public network according to the service information of the service request or the first indication information which is sent by the first network element in the first public network and aims at the service request.

In a second aspect, an embodiment of the present application provides a service request method, including: a first network element in a first public network sends first indication information to terminal equipment according to a service request sent by the terminal equipment, wherein the terminal equipment resides in a non-public network;

the first indication information is used for the terminal equipment to establish connection with a third network element in the second public network through the second network element in the non-public network.

In a third aspect, an embodiment of the present application provides a service request method, including: a third network element in a second public network receives a service request sent by terminal equipment, wherein the terminal equipment resides in a non-public network; the third network element determines whether to establish a service connection for the service request.

In a fourth aspect, an embodiment of the present application provides a terminal device, including: the first processing unit is configured to establish connection with a third network element in the second public network through the second network element in the non-public network according to service information of the service request or first indication information which is sent by the first network element in the first public network and aims at the service request.

In a fifth aspect, an embodiment of the present application provides a first network element, where the first network element is located in a first public network, and the first network element includes:

the third sending unit is configured to send first indication information to the terminal equipment according to a service request sent by the terminal equipment, wherein the terminal equipment resides in a non-public network;

In a sixth aspect, an embodiment of the present application provides a third network element, where the third network element is located in a second public network, and the third network element includes:

the second receiving unit is configured to receive a service request sent by terminal equipment, wherein the terminal equipment resides in a non-public network;

And a fourth processing unit configured to determine whether to establish a service connection for the service request.

In a seventh aspect, an embodiment of the present application provides a terminal device, including a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to execute steps of a service request method executed by the terminal device when the computer program is run.

In an eighth aspect, an embodiment of the present application provides a first network element, including a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to execute, when running the computer program, the steps of a service request method executed by the first network element.

In a ninth aspect, an embodiment of the present application provides a third network element, including a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to execute the steps of the service request method executed by the third network element when the computer program is run.

In a tenth aspect, an embodiment of the present application provides a storage medium storing an executable program, where the executable program when executed by a processor implements the service request method executed by the terminal device.

In an eleventh aspect, an embodiment of the present application provides a storage medium storing an executable program, where the executable program when executed by a processor implements the service request method executed by the first network element.

In a twelfth aspect, an embodiment of the present application provides a storage medium storing an executable program, where the executable program when executed by a processor implements the service request method executed by the third network element.

In a thirteenth aspect, an embodiment of the present application provides a chip, including: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the service request method executed by the terminal device.

In a fourteenth aspect, an embodiment of the present application provides a chip, including: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the service request method executed by the first network element.

In a fifteenth aspect, an embodiment of the present application provides a chip, including: and the processor is used for calling and running the computer program from the memory so that the device provided with the chip executes the service request method.

In a sixteenth aspect, an embodiment of the present application provides a computer program product comprising computer program instructions for causing a computer to perform the service request method described above.

A seventeenth aspect is a computer program for causing a computer to execute the service request method as described above.

The service request method provided by the embodiment of the application comprises the following steps: and the terminal equipment residing in the non-public network establishes connection with a third network element in the second public network through the second network element in the non-public network according to the service information or the first indication information sent by the first network element in the first public network. Therefore, the terminal equipment residing in the non-public network can carry out service request to the public network, and the service range of the terminal equipment residing in the non-public network is expanded.

Drawings

Fig. 1 is a schematic diagram of a terminal device accessing to a PLMN network through NPN in the present application;

fig. 2 is a schematic diagram of a terminal device accessing an LTE system through a non-3 GPP network according to the present application;

fig. 3 is another schematic diagram of a terminal device accessing an LTE system through a non-3 GPP network according to the present application;

fig. 4 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 5 is a schematic diagram of an alternative processing flow of the service request method applied to the terminal device in the present application;

fig. 6 is a schematic diagram of an alternative processing flow of a service request method applied to a first network element according to an embodiment of the present application;

Fig. 7 is a schematic diagram of an alternative processing flow of a service request method applied to a third network element according to an embodiment of the present application;

fig. 8 is a schematic diagram of a network architecture of a service request method applied to a communication system according to an embodiment of the present application;

fig. 9 is a schematic diagram of another network architecture of a service request method applied to a communication system according to an embodiment of the present application;

fig. 10 is a schematic diagram of still another network architecture of a service request method applied to a communication system according to an embodiment of the present application;

fig. 11 is a schematic diagram of still another network architecture of a service request method applied to a communication system according to an embodiment of the present application;

fig. 12 is a schematic diagram of a composition structure of a terminal device according to an embodiment of the present application;

fig. 13 is a schematic diagram of a composition structure of a first network element according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a third network element according to an embodiment of the present application;

fig. 15 is a schematic diagram of a hardware composition structure of an electronic device according to an embodiment of the present application.

Detailed Description

So that the manner in which the features and techniques of the embodiments of the present application can be understood in more detail, a more particular description of the application, briefly summarized below, may be had by reference to the appended drawings, which are not intended to be limiting of the embodiments of the present application.

Before the service request method provided by the embodiment of the application is described in detail, a brief description is given to a public network and a non-public network.

In long term evolution (Long Term Evolution, LTE) networks and New Radio (NR) networks, public networks, namely public land mobile networks (Public Land Mobile Network, PLMNs), are typically deployed. However, in some scenarios, such as office scenarios, home scenarios, factories, etc., in order to more effectively perform network security management, a local network or a private network is typically deployed; the local network and the private network are also referred to as non-public networks.

Part of the services of the terminal device can only be implemented in public networks, like IP multimedia (IP Multimedia Subsystem, IMS) services. Therefore, in implementing IMS services, terminal devices residing in non-public networks need to access into the public network. As shown in fig. 1, the procedure of accessing the terminal device to the PLMN network through NPN is that the terminal device establishes a data transmission channel between the terminal device and a Non-3GPP interworking function (Non-3GPP InterWorking Function,N3IWF) entity in the PLMN through a user plane function (User Plane Function, UPF) entity in the NPN network, so that the terminal device can interact with PLMN entities such as an access and mobility management function (Access and Mobility Management Function, AMF) entity, a UPF entity and the like in the PLMN. However, in some scenarios, the NR system of the PLMN network may not support the service to be transmitted by the terminal device, but the LTE system of the PLMN network may support the service to be transmitted by the terminal device, such as an IMS voice service. In this scenario, a terminal device residing in a non-public network needs to access the LTE system.

The terminal device can access the LTE system through the non-3 GPP network, and the terminal device accesses a schematic diagram of the LTE system through the non-3 GPP network, as shown in fig. 2, the terminal device first establishes a data transmission link with the ePDG, the ePDG also establishes a data transmission link with the PDN GW, and data sent by the terminal device is sent to the PDN GW through the ePDG and sent to a service domain of an operator through the PDN GW. The terminal device accesses another schematic diagram of the LTE system through the non-3 GPP network, as shown in fig. 3, the terminal device establishes a data transmission link with the PDN GW, and the data sent by the terminal device is first sent to the PDN GW, and then sent to the service domain of the operator by the PDN GW.

The application provides a service request method, which can be accessed to a public network through a 3GPP non-public network, and can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) systems, general packet radio service (General Packet Radio Service, GPRS), LTE systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) communication systems, or 5G systems, etc.

An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 4. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Alternatively, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. "terminal device" as used herein includes, but is not limited to, a connection via a wireline, such as via a public-switched telephone network (Public Switched Telephone Networks, PSTN), a digital subscriber line (Digital Subscriber Line, DSL), a digital cable, a direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (Wireless Local Area Network, WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of the other terminal device arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminal devices arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal device may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved PLMN, etc.

Alternatively, direct terminal (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

Fig. 4 exemplarily shows one network device and two terminal devices, alternatively, the communication system 100 may include a plurality of network devices and each network device may include other number of terminal devices within a coverage area of the network device, which is not limited by the embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 4 as an example, the communication device may include the network device 110 and the terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be the specific devices described above, which are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

An optional processing flow of the service request method applied to the terminal device provided by the embodiment of the application, as shown in fig. 5, includes the following steps:

step S201, terminal equipment residing in a non-public network establishes connection with a third network element in a second public network through the second network element in the non-public network according to service information of a service request or first indication information which is sent by a first network element in the first public network and aims at the service request.

In some embodiments, the service request is a service request sent by the terminal device to the network device for a service to be processed, the first public network is an NR network, the second public network is an LTE network, the first network element is an N3IWF entity, and the second network element is a UPF entity.

In some embodiments, the third network element is an ePDG. The terminal equipment residing in the non-public network determines third network element information according to the service information; such as determining ePDG and PDN GW. Wherein, the service information may be a service type. The corresponding relation between the service information and the ePDG information can be preconfigured; in specific implementation, the correspondence between the service information and the ePDG information and PDN GW information may be preconfigured in the terminal device in the form of a list. An interface exists between a UPF entity in a non-public network and the ePDG, and the terminal equipment establishes connection with the ePDG, such as IP connection, through the UPF entity; and the terminal equipment sends a service request to the ePDG, and sends PDN GW information selected by the terminal equipment to the ePDG. The method comprises the steps that an ePDG sends a service request to a PDN GW, and terminal equipment establishes connection with the PDN GW through the ePDG; and the PDN GW judges whether to establish connection for the service corresponding to the service request according to the subscription information and the network policy information of the terminal equipment. Wherein the subscription information of the terminal device may be obtained from a home subscriber server (Home Subscriber Server, HSS) and the network policy information may be obtained from a policy and charging rules function (Policy and Charging Rules Function, PCRF) entity.

In other alternative embodiments, the third network element is a PDN GW. The terminal device residing in the non-public network determines third network element information, such as PDN GW, from the traffic information. Wherein, the service information may be a service type. The corresponding relation between the service information and the PDN GW information can be preconfigured; in specific implementation, the correspondence between the service information and the PDN GW information may be preconfigured in the terminal device in the form of a list. An interface exists between a UPF entity in a non-public network and a PDN GW, and terminal equipment establishes connection with the PDN GW through the UPF entity, such as IP connection; the terminal equipment sends a service request to the PDN GW, and the PDN GW judges whether to establish connection for the service corresponding to the service request according to the subscription information and the network policy information of the terminal equipment. The subscription information of the terminal device may be obtained from the HSS, and the network policy information may be obtained from a PCRF entity.

In yet other alternative embodiments, there is an interface between a UPF entity and an N3IWF entity in a non-public network, and the terminal device sends, through the second network element, a service request to the first network element; i.e. the terminal device sends a service request to the N3IWF entity via the UPF entity. After receiving a service request sent by a terminal device, an N3IWF entity confirms that a first public network where the N3IWF entity is located does not support the service in the service request, the N3IWF entity selects PDN GW corresponding to the service in the service request according to the corresponding relation between service information and PDN GW information and/or selects ePDG corresponding to the service in the service request according to the corresponding relation between the service information and the ePDG information; the N3IWF entity sends the ePDG and/or the ePDG to the terminal equipment through the first indication information.

In still other alternative embodiments, there is an interface between a UPF entity and an N3IWF entity in a non-public network, and the terminal device sends, through the second network element, a service request to the first network element; i.e. the terminal device sends a service request to the N3IWF entity via the UPF entity. After receiving a service request sent by a terminal device, an N3IWF entity confirms that a first public network where the N3IWF entity is located does not support a service in the service request, and then the N3IWF entity does not support the service requested by the terminal device by the first public network, or the terminal device sends the service request to the second public network and sends the service request to the terminal device through first indication information.

An optional processing flow of the service request method applied to the first network element provided in the embodiment of the present application, as shown in fig. 6, includes the following steps:

step S301, a first network element in a first public network sends first indication information to a terminal device according to a service request sent by the terminal device, where the first indication information is used for the terminal device to establish a connection with a third network element in a second public network through a second network element in the non-public network.

In some embodiments, the first public network is an NR network, the second public network is an LTE network, the first network element is an N3IWF entity, and the second network element is a UPF entity. The terminal device resides in a non-public network. An interface exists between a UPF entity and an N3IWF entity in a non-public network, and the terminal equipment sends a service request to the first network element through the second network element; i.e. the terminal device sends a service request to the N3IWF entity via the UPF entity. The N3IWF entity determines that the first public network does not support the service requested by the terminal device. In the implementation, after receiving a service request sent by a terminal device, an N3IWF entity confirms that a first public network where the N3IWF entity is located does not support a service in the service request, which may be implemented by any one of the following modes: 1) The fourth network element sends second indication information to the N3IWF entity, and the second indication information indicates that the first public network does not support the service in the service request; the fourth network element may be an AMF entity or an SMF entity. 2) The N3IWF entity pre-stores policies including services not supported by the first public network. 3) Quality of service (Quality of Service, qoS) of the service supported by the N3IWF entity.

In some optional embodiments, the first indication information is used to indicate that the first public network does not support the service requested by the terminal device, or the first indication information is used to indicate that the terminal device sends the service request to the second public network.

In other optional embodiments, the first indication information is used to indicate information of the third network element; the first indication information is further used for indicating that the service link corresponding to the service request is switched to the second public network.

When the third network element is a PDN GW, the N3IWF entity selects the PDN GW corresponding to the service in the service request according to the corresponding relation between the service information and the PDN GW information; the corresponding relation between the service information and the PDN GW information may be preconfigured, and the service information may be a service type. The N3IWF entity establishes a data transmission channel between the terminal equipment and the PDN GW by establishing connection with the PDN GW. The N3IWF entity may also send the determined PDN GW information to the terminal device. The data of the terminal equipment residing in the non-public network is sent to an N3IWF entity in the first public network through a UPF entity, and the N3IWF entity sends the data to a PDN GW in the second public network; in this way, data of the terminal device residing in the non-public network is made to access the second public network.

And when the third network element is an ePDG, the N3IWF entity selects the ePDG corresponding to the service in the service request according to the corresponding relation between the service information and the ePDG information, and selects the PDN GW corresponding to the service in the service request according to the corresponding relation between the service information and the PDN GW information. The corresponding relation between the service information and the ePDG information and the corresponding relation between the service information and the PDN GW information may be preconfigured, and the service information may be a service type. The N3IWF entity establishes connection with the ePDG, so that data sent by the terminal equipment is sent to the ePDG through the N3IWF entity and then sent to the PDN GW by the ePDG, and a data transmission channel between the terminal equipment and the PDN GW is further established. The N3IWF entity may also send the determined PDN GW information to the terminal device. The data of the terminal equipment residing in the non-public network is sent to an N3IWF entity in the first public network through a UPF entity, and the N3IWF entity sends the data to a PDN GW in the second public network; in this way, data of the terminal device residing in the non-public network is made to access the second public network.

An optional processing flow of the service request method applied to the third network element provided in the embodiment of the present application, as shown in fig. 7, includes the following steps:

In step S401, a third network element in the second public network receives a service request sent by the terminal device.

In some embodiments, the terminal device resides in a non-public network.

In step S402, the third network element determines whether to establish a service connection for the service request.

In some embodiments, the third network element directly determines whether to establish a service connection for the service request, i.e. the third network element itself determines whether to establish a service connection for the service request.

In other embodiments, the third network element sends the service request to a fifth network element in the second public network; and the third network element determines whether to establish service connection for the service request according to the information sent by the fifth network element. Determining whether to establish service connection for the service request by a fifth network element according to the service request; and the fifth network element sends the confirmed information whether to establish service connection for the service request to the third network element.

Whether to establish service connection for the service request is determined according to subscription information and/or network policy information of the terminal equipment. The subscription information of the terminal equipment is obtained from a sixth network element, and/or the network policy information is obtained from a seventh network element. The fifth network element comprises a service gateway, the sixth network element is an HSS, and the seventh network element is a PCRF entity. The third network element comprises an ePDG, the third network element comprises a PDN GW.

In other embodiments, the second public network is an LTE network.

The network architecture of the service request method applied to the communication system provided by the embodiment of the application is shown in fig. 8, and based on the network architecture shown in fig. 8, the processing flow of accessing the terminal equipment residing in the non-public network to the second public network is as follows:

the terminal equipment selects an ePDG and a PDN WG according to the service type to be established, and establishes connection between the terminal equipment and the ePDG, such as IP connection, through a UPF entity in a non-public network; the terminal device may also send PDN WG information to the ePDG, which establishes a connection with the PDN WG. The PDN WG judges whether to establish connection for the service according to the subscription information and the network policy information of the terminal equipment, or the PDN WG sends a service request of the terminal equipment to a service gateway, and the service gateway judges whether to establish connection for the service according to the subscription information and the network policy information of the terminal. The subscription information of the terminal device can be obtained from the HSS, and the network policy information can be obtained by using the PCRF. In specific implementation, the terminal device establishes a dedicated PDN connection for the ePDG in the non-public network, and establishes an IP channel between the terminal device and the ePDG on the dedicated PDN connection. In the implementation, the corresponding relation between the service type and the ePDG information and the corresponding relation between the service type and the PDN GW information may be preconfigured. The correspondence between the service type and the ePDG information, and between the service type and the PDN GW information may be preconfigured in the terminal device in the form of a list.

As shown in fig. 9, based on the network architecture shown in fig. 9, the processing flow of accessing a terminal device residing in a non-public network to a second public network is as follows:

the terminal equipment selects PDN WG according to the service type which needs to be established, and establishes connection between the terminal equipment and the PDN WG through a UPF entity in a non-public network, such as IP connection. The PDN WG judges whether to establish connection for the service according to the subscription information and the network policy information of the terminal equipment, or the PDN WG sends a service request of the terminal equipment to a service gateway, and the service gateway judges whether to establish connection for the service according to the subscription information and the network policy information of the terminal. The subscription information of the terminal device can be obtained from the HSS, and the network policy information can be obtained by using the PCRF. In specific implementation, the terminal device establishes a dedicated PDN connection for the PDN WG in the non-public network, and establishes an IP channel between the terminal device and the PDN WG on the dedicated PDN connection. In the implementation, the corresponding relation between the service type and the PDN GW information can be preconfigured. The correspondence between the service types and the PDN GW information may be preconfigured in the terminal device in the form of a list.

As shown in fig. 10, based on the network architecture shown in fig. 10, the processing flow of accessing the terminal device residing in the non-public network to the second public network is as follows:

the terminal device accesses to a first public network of the PLMN network through a UPF entity in the non-public network, the first public network not supporting services requested by the terminal device, such as IMS services. The first public network switches the service request of the terminal device to a second public network of the PLMN network. In a specific implementation, an N3IWF entity in the first public network establishes a connection with a PDN GW and sends PDN GW information to the terminal device. When the terminal equipment sends data to the N3IWF entity, carrying PDN GW information; the N3IWF entity transmits the data transmitted by the terminal equipment to the PDN GW. In a specific implementation, the service requested by the first public network not supporting the terminal device may be determined by the N3IWF entity; such as: 1) The fourth network element sends second indication information to the N3IWF entity, and the second indication information indicates that the first public network does not support the service in the service request; the fourth network element may be an AMF entity or an SMF entity. 2) The N3IWF entity pre-stores policies including services not supported by the first public network. 3) QoS for services supported by the N3IWF entity.

In some embodiments, an N3IWF entity in the first public network establishes a connection with an ePDG and sends ePDG information and PDN GW information to the terminal device. When the terminal equipment sends data to the N3IWF entity, carrying ePDG information and PDN GW information; the N3IWF entity sends the data sent by the terminal equipment to the ePDG, and the ePDG sends the final data to the PDN GW. In a specific implementation, the service requested by the first public network not supporting the terminal device may be determined by the N3IWF entity; such as: 1) The fourth network element sends second indication information to the N3IWF entity, and the second indication information indicates that the first public network does not support the service in the service request; the fourth network element may be an AMF entity or an SMF entity. 2) The N3IWF entity pre-stores policies including services not supported by the first public network. 3) QoS for services supported by the N3IWF entity.

As shown in fig. 11, based on the network architecture shown in fig. 11, the processing flow of accessing the terminal device residing in the non-public network to the second public network is as follows:

the terminal device accesses to a first public network of the PLMN network through a UPF entity in the non-public network, the first public network not supporting services requested by the terminal device, such as IMS services. The first public network switches the service request of the terminal device to a second public network of the PLMN network. In a specific implementation, an N3IWF entity in a first public network sends first indication information to a terminal device, where the first indication information is used to indicate that the first public network does not support a service requested by the terminal device, or the first indication information is used to indicate that the terminal device sends the service request to the second public network. After receiving the first indication information, the terminal equipment establishes connection with the ePDG and/or the PDN GW in the second public network. The process of the terminal device establishing a connection with the ePDG and/or PDN GW in the second public network is the same as the process of the terminal device establishing a connection with the ePDG and/or PDN GW in the second public network based on the network architecture shown in fig. 8, and is not described here again.

The service request method provided by the application can realize that the terminal equipment residing in the non-public network accesses to the specific public network according to the service information corresponding to the service request or according to the first indication information sent by the first network element, thereby expanding the service range of the terminal equipment residing in the non-public network.

In order to implement the service request method, an embodiment of the present application provides a terminal device, where a composition structure of the terminal device 500, as shown in fig. 12, includes:

the first processing unit 501 is configured to establish, according to service information of a service request or first indication information sent by a first network element in a first public network and aiming at the service request, a connection with a third network element in a second public network through a second network element in the non-public network.

In some embodiments, the second network element is a UPF entity.

In some embodiments, the three network elements comprise epdgs or PDN GWs.

In some embodiments, the terminal device 500 further comprises: a first sending unit 502, configured to send, through the second network element, a service request to the first network element.

In some embodiments, the terminal device 500 further comprises: a first receiving unit 503, configured to receive first indication information sent by the first network element; the first indication information is used for indicating information of the third network element, or the first indication information is used for indicating that the first public network does not support the service requested by the terminal equipment, or the first indication information is used for indicating the terminal equipment to send the service request to the second public network.

In some embodiments, the first processing unit 501 is further configured to determine information of the third network element according to the service information.

In some embodiments, the information of the third network element includes: ePDG information and/or PDN GW information.

In some embodiments, the terminal device 500 further comprises: a second sending unit 504 is configured to send the PDN GW information to an ePDG.

In some embodiments, the correspondence between the service information and the ePDG information is preconfigured; and/or, the corresponding relation between the service information and the PDN GW information is preconfigured.

In some embodiments, the first network element comprises an N3IWF entity, the first public network is a NR network, and the second public network is an LTE network.

In order to implement the above service request method, an embodiment of the present application provides a first network element, where the first network element is located in a first public network, and a composition structure of the first network element 600 is shown in fig. 13, and includes:

a third sending unit 601, configured to send, according to a service request sent by a terminal device, first indication information to the terminal device, where the terminal device resides in a non-public network;

In some embodiments, the first indication information is used to indicate information of the third network element.

In some embodiments, the first indication information is further used to indicate that a service link corresponding to the service request is switched to the second public network.

In some embodiments, the first network element further comprises: a second processing unit 602 configured to establish a connection with the third network element.

In some embodiments, the first indication information is used to indicate that the first public network does not support the service requested by the terminal device, or the first indication information is used to indicate that the terminal device sends the service request to the second public network.

In some embodiments, the first network element 600 further comprises: a third processing unit 603 is configured to determine that the first public network does not support the service requested by the terminal device.

In some embodiments, the first public network does not support the service requested by the terminal device is determined by any one of the following:

second indication information sent by a fourth network element in the first public network;

the first network element pre-stores strategies;

QoS of services supported by the first network element.

In some embodiments, the fourth network element comprises an access and mobility management function, AMF, entity or a session management function, SMF, entity.

In some embodiments, the first network element comprises an N3IWF entity.

In some embodiments, the second network element comprises a UPF entity.

In some embodiments, the third network element comprises an ePDG or a PDN GW.

In some embodiments, the first public network is a NR network and the second public network is an LTE network.

In order to implement the service request method, an embodiment of the present application provides a third network element, where the third network element is located in the second public network, and a composition structure of the third network element 700 is shown in fig. 14, and includes:

a second receiving unit 701, configured to receive a service request sent by a terminal device, where the terminal device resides in a non-public network;

a fourth processing unit 702 is configured to determine whether to establish a service connection for the service request.

In some embodiments, the fourth processing unit 702 is configured to directly determine whether to establish a service connection for the service request.

In some embodiments, the fourth processing unit 702 is configured to send the service request to a fifth network element in the second public network;

And determining whether to establish service connection for the service request according to the information sent by the fifth network element.

In some embodiments, whether to establish a service connection for the service request is determined according to subscription information and/or network policy information of the terminal device.

In some embodiments, the subscription information of the terminal device is obtained from a sixth network element; and/or, the network policy information is obtained from a seventh network element.

In some embodiments, the fifth network element comprises: and (5) a service gateway.

In some embodiments, the sixth network element comprises: HSS; the seventh network element comprises: and the PCRF entity.

In some embodiments, the third network element comprises an ePDG, or the third network element comprises a PDN GW.

In some embodiments, the second public network is an LTE network.

The embodiment of the application also provides the terminal equipment, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the service request method executed by the terminal equipment when the computer program runs.

The embodiment of the application also provides a first network element, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the service request method executed by the first network element when the computer program runs.

The embodiment of the application also provides a third network element, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the service request method executed by the third network element when the computer program runs.

Fig. 15 is a schematic diagram of a hardware composition structure of an electronic device (a terminal device, a first network element, and a third network element) according to an embodiment of the present application, where an electronic device 700 includes: at least one processor 701, memory 702, and at least one network interface 704. The various components in the electronic device 700 are coupled together by a bus system 705. It is appreciated that the bus system 705 is used to enable connected communications between these components. The bus system 705 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration, the various buses are labeled as bus system 705 in fig. 15.

It is to be appreciated that the memory 702 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. Wherein the nonvolatile Memory may be ROM, programmable read-Only Memory (PROM, programmable Read-Only Memory), erasable programmable read-Only Memory (EPROM, erasable Programmable Read-Only Memory), electrically erasable programmable read-Only Memory (EEPROM, electrically Erasable Programmable Read-Only Memory), magnetic random access Memory (FRAM, ferromagnetic random access Memory), flash Memory (Flash Memory), magnetic surface Memory, optical disk, or compact disk read-Only Memory (CD-ROM, compact Disc Read-Only Memory); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be random access memory (RAM, random Access Memory), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (SRAM, static Random Access Memory), synchronous static random access memory (SSRAM, synchronous Static Random Access Memory), dynamic random access memory (DRAM, dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (ddr SDRAM, double Data Rate Synchronous Dynamic Random Access Memory), enhanced synchronous dynamic random access memory (ESDRAM, enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, syncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, direct Rambus Random Access Memory). The memory 702 described in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The memory 702 in embodiments of the application is used to store various types of data to support the operation of the electronic device 700. Examples of such data include: any computer program for operating on the electronic device 700, such as application 7022. A program for implementing the method of the embodiment of the present application may be contained in the application program 7022.

The method disclosed in the above embodiment of the present application may be applied to the processor 701 or implemented by the processor 701. The processor 701 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in the processor 701 or by instructions in the form of software. The processor 701 may be a general purpose processor, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 701 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the application can be directly embodied in the hardware of the decoding processor or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium in a memory 702. The processor 701 reads information in the memory 702 and, in combination with its hardware, performs the steps of the method as described above.

In an exemplary embodiment, the electronic device 700 can be implemented by one or more application specific integrated circuits (ASIC, application Specific Integrated Circuit), DSP, programmable logic device (PLD, programmable Logic Device), complex programmable logic device (CPLD, complex Programmable Logic Device), FPGA, general purpose processor, controller, MCU, MPU, or other electronic components for performing the aforementioned methods.

The embodiment of the application also provides a storage medium for storing the computer program.

Optionally, the storage medium may be applied to a terminal device in the embodiment of the present application, and the computer program makes a computer execute corresponding flows in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the storage medium may be applied to the first network element in the embodiment of the present application, and the computer program causes a computer to execute corresponding flows in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the storage medium may be applied to the third network element in the embodiment of the present application, and the computer program causes a computer to execute corresponding flows in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a chip, which comprises: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the service request method executed by the first network element.

The embodiment of the application also provides a chip, which comprises: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the service request method executed by the third network element.

The embodiment of the application also provides a computer program product, which comprises computer program instructions, and the computer program instructions enable a computer to execute corresponding processes in the methods of the embodiment of the application, and for brevity, the description is omitted here.

Optionally, the computer program product may be applied to a terminal device in the embodiment of the present application, and the computer program makes a computer execute corresponding flows in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program product may be applied to the first network element in the embodiment of the present application, and the computer program causes a computer to execute corresponding flows in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to the third network element in the embodiment of the present application, and the computer program causes a computer to execute corresponding flows in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program which enables the computer terminal equipment to execute the service request method.

The embodiment of the application also provides a computer program which enables the first network element of the computer to execute the service request method.

The embodiment of the application also provides a computer program which enables the third network element of the computer to execute the service request method.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is not intended to limit the scope of the application, but is intended to cover any modifications, equivalents, and improvements within the spirit and principles of the application.

Claims

1. A service request method, the method comprising:

The terminal equipment residing in the non-public network establishes connection with a third network element in the second public network through the second network element in the non-public network according to the service information of the service request or the first indication information which is sent by the first network element in the first public network and aims at the service request; the first public network is a new wireless NR network, and the second public network is a long term evolution LTE network; the service information corresponds to third network element information of the third network element;

the method comprises the steps that a terminal device residing in a non-public network establishes connection with a third network element in a second public network through a second network element in the non-public network according to first indication information which is sent by a first network element in the first public network and aims at the service request, and the method further comprises the following steps:

the terminal equipment sends the service request to the first network element, so that the first network element sends the first indication information to the terminal equipment under the condition that the first public network does not support the service request.

2. The method of claim 1, wherein the second network element is a user plane function, UPF, entity.

3. The method of claim 1 or 2, wherein the third network element comprises an evolved packet data gateway, ePDG.

4. The method according to claim 1 or 2, wherein the third network element comprises a packet data gateway, PDN GW.

5. The method according to claim 1 or 2, wherein the method further comprises:

and the terminal equipment sends a service request to the first network element through the second network element.

6. The method according to claim 1 or 2, wherein the method further comprises:

the terminal equipment receives first indication information sent by the first network element;

the first indication information is used for indicating information of the third network element, or the first indication information is used for indicating that the first public network does not support the service requested by the terminal equipment, or the first indication information is used for indicating the terminal equipment to send the service request to the second public network.

7. The method according to claim 1 or 2, wherein the method further comprises:

and the terminal equipment determines the information of the third network element according to the service information.

8. The method of claim 7, wherein the information of the third network element comprises:

ePDG information and/or PDN GW information.

9. The method of claim 8, wherein the method further comprises:

And the terminal equipment sends the PDN GW information to an ePDG.

10. The method of any one of claim 1, 2, 8, or 9, wherein,

the corresponding relation between the service information and the ePDG information is pre-configured;

and/or, the corresponding relation between the service information and the PDN GW information is preconfigured.

11. The method of any of claims 1, 2, 8, or 9, wherein the first network element comprises a non-3 GPP interworking function, N3IWF, entity.

12. A network access method, the method comprising:

a first network element in a first public network sends first indication information to terminal equipment when the first public network does not support a service request according to the service request sent by the terminal equipment, wherein the terminal equipment resides in a non-public network;

the first indication information is used for the terminal equipment to establish connection with a third network element in the second public network through the second network element in the non-public network;

the first public network is a new wireless NR network, and the second public network is a long term evolution LTE network.

13. The method of claim 12, wherein the first indication information is used to indicate information of the third network element.

14. The method according to claim 12 or 13, wherein the first indication information is further used to indicate that a service link corresponding to the transmission of the service request has been switched to the second public network.

15. The method according to claim 12 or 13, wherein the method further comprises:

and the first network element establishes connection with the third network element.

16. The method of claim 12, wherein the first indication information is used to indicate that the first public network does not support the service requested by the terminal device, or the first indication information is used to indicate that the terminal device sends the service request to the second public network.

17. The method of any of claims 12, 13, or 16, wherein the method further comprises:

the first network element determines that the first public network does not support the service requested by the terminal device.

18. The method of claim 17, wherein the first public network does not support the service requested by the terminal device is determined by any one of:

the first network element pre-stores strategies;

Quality of service, qoS, of the service supported by the first network element.

19. The method of claim 18, wherein the fourth network element comprises an access and mobility management function, AMF, entity or a session management function, SMF, entity.

20. The method of any of claims 12, 13, 16, 18, or 19, wherein the first network element comprises a non-3 GPP interworking function, N3IWF, entity.

21. The method of any one of claims 12, 13, 16, 18, or 19, wherein the second network element comprises a user plane function, UPF, entity.

22. The method of any one of claims 12, 13, 16, 18, or 19, wherein the third network element comprises an evolved packet data gateway, ePDG;

alternatively, the third network element comprises a packet data gateway PDN GW.

23. A network access method, the method comprising:

a third network element in a second public network receives a service request sent by terminal equipment, wherein the terminal equipment resides in a non-public network; the third network element is determined by the terminal equipment according to the service information of the service request;

the third network element determines whether to establish a service connection for the service request;

wherein the second public network is a long term evolution, LTE, network.

24. The method of claim 23, wherein the third network element determining whether to establish a service connection for the service request comprises:

the third network element directly determines whether to establish a service connection for the service request.

25. The method of claim 23, wherein the third network element determining whether to establish a service connection for the service request comprises:

the third network element sends the service request to a fifth network element in the second public network;

and the third network element determines whether to establish service connection for the service request according to the information sent by the fifth network element.

26. The method according to claim 24 or 25, wherein whether or not a service connection is established for the service request is determined according to subscription information and/or network policy information of the terminal device.

27. The method of claim 26, wherein the subscription information of the terminal device is obtained from a sixth network element;

and/or, the network policy information is obtained from a seventh network element.

28. The method of claim 25, wherein the fifth network element comprises: and (5) a service gateway.

29. The method of claim 27, wherein the sixth network element comprises: home subscriber server HSS;

And/or, the seventh network element comprises: policy and charging rules function PCRF entity.

30. The method of any one of claims 23 to 25, or any one of claims 27-29, wherein the third network element comprises an evolved packet data gateway, ePDG;

31. A terminal device residing in a non-public network, the terminal device comprising:

the first processing unit is configured to establish connection with a third network element in a second public network through the second network element in the non-public network according to service information of a service request or first indication information which is sent by a first network element in the first public network and aims at the service request;

wherein the first public network is a new wireless NR network, and the second public network is a long term evolution LTE network; the service information corresponds to third network element information of the third network element;

the first processing unit is further configured to send the service request to a first network element in the non-public network before connection with a third network element in the second public network is established through the second network element in the first public network according to first indication information sent by the first network element in the first public network, so that the first indication information is sent to the terminal device when the first network element determines that the first public network does not support the service request.

32. The terminal device of claim 31, wherein the second network element is a user plane function UPF entity.

33. The terminal device of claim 31 or 32, wherein the third network element comprises an evolved packet data gateway, ePDG.

34. The terminal device of claim 31 or 32, wherein the third network element comprises a packet data gateway, PDN GW.

35. The terminal device of claim 31 or 32, wherein the terminal device further comprises:

and the first sending unit is configured to send a service request to the first network element through the second network element.

36. The terminal device of claim 31 or 32, wherein the terminal device further comprises:

a first receiving unit configured to receive first indication information sent by the first network element;

37. The terminal device according to claim 31 or 32, wherein the first processing unit is further configured to determine information of the third network element according to the service information.

38. The terminal device of claim 34, wherein the information of the third network element includes:

ePDG information and/or PDN GW information.

39. The terminal device of claim 38, wherein the terminal device further comprises:

and a second sending unit configured to send the PDN GW information to an ePDG.

40. The terminal device of any of claims 31, 32, 38, or 39, wherein the correspondence between the traffic information and ePDG information is preconfigured;

41. A terminal device as defined in any one of claims 31, 32, 38, or 39, wherein the first network element comprises a non-3 GPP interworking function, N3IWF, entity.

42. A first network element located in a first public network, the first network element comprising:

a third sending unit, configured to send first indication information to a terminal device, where the first public network does not support the service request according to the service request sent by the terminal device, and the terminal device resides in a non-public network;

43. The first network element of claim 42, wherein the first indication information is used to indicate information of the third network element.

44. The first network element of claim 42 or 43, wherein the first indication information is further used to indicate that a service link corresponding to the transmission of the service request has been switched to the second public network.

45. The first network element of claim 42 or 43, wherein the first network element further comprises:

and the second processing unit is configured to establish connection with the third network element.

46. A first network element according to claim 42, wherein the first indication information is used to indicate that the first public network does not support the service requested by the terminal device, or the first indication information is used to indicate that the terminal device sends the service request to the second public network.

47. The first network element of any one of claims 42, 43, or 46, wherein the first network element further comprises:

and a third processing unit configured to determine that the first public network does not support the service requested by the terminal device.

48. The first network element of claim 47, wherein the first public network does not support the service requested by the terminal device is determined by any one of:

the first network element pre-stores strategies;

quality of service, qoS, of the service supported by the first network element.

49. The first network element of claim 48, wherein the fourth network element comprises an access and mobility management function, AMF, entity or a session management function, SMF, entity.

50. A first network element as recited in any of claims 42, 43, 46, 48, or 49, wherein the first network element comprises a non-3 GPP interworking function, N3IWF, entity.

51. The first network element of any one of claims 42, 43, 46, 48, or 49, wherein the second network element comprises a user plane function, UPF, entity.

52. The first network element of any one of claims 42, 43, 46, 48, or 49, wherein the third network element comprises an evolved packet data gateway, ePDG;

53. A third network element, which is located in the second public network, and is determined by the terminal device according to the service information of the service request; the third network element comprises:

a fourth processing unit configured to determine whether to establish a service connection for the service request;

wherein the second public network is a long term evolution, LTE, network.

54. The third network element of claim 53, wherein the fourth processing unit is configured to directly determine whether to establish a service connection for the service request.

55. The third network element of claim 53, wherein the fourth processing unit is configured to send the service request to a fifth network element in the second public network;

56. A third network element according to claim 54 or 55, wherein whether or not a service connection is established for the service request is determined based on subscription information and/or network policy information of the terminal device.

57. The third network element of claim 56, wherein the subscription information of the terminal device is obtained from a sixth network element;

58. The third network element of claim 55, wherein the fifth network element comprises: and (5) a service gateway.

59. The third network element of claim 57, wherein the sixth network element comprises: home subscriber server HSS;

60. The third network element of any one of claims 53 to 55, or any one of claims 57-59, wherein the third network element comprises an evolved packet data gateway, ePDG;

61. A terminal device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor being arranged to execute the steps of the service request method of any of claims 1 to 11 when the computer program is run.

62. A first network element comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor being arranged to execute the steps of the service request method of any of claims 12 to 22 when the computer program is run.

63. A third network element comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor being arranged to execute the steps of the service request method of any of claims 23 to 30 when the computer program is run.

64. A storage medium storing an executable program which, when executed by a processor, implements the service request method of any one of claims 1 to 11.

65. A storage medium storing an executable program which, when executed by a processor, implements the service request method of any one of claims 12 to 22.

66. A storage medium storing an executable program which, when executed by a processor, implements the service request method of any one of claims 23 to 30.

67. A chip, comprising: a processor for calling and running a computer program from a memory, so that a device on which the chip is mounted performs the service request method according to any one of claims 1 to 11.

68. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the service request method according to any one of claims 12 to 22.

69. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the service request method according to any one of claims 23 to 30.