Wireless communication method, device, equipment, storage medium and program product

Abstract

The invention discloses a wireless communication method and device, equipment, a storage medium and a program product, and relates to the technical field of communication. The method comprises the following steps that: remote terminal equipment sends an SIP (Session Initiation Protocol) registration request message to relay terminal equipment, wherein the SIP registration request message is sent to a first core network element in a network by the relay terminal equipment; wherein the SIP registration request message comprises first information, and the first information is used for instructing the remote terminal device to access the network in a relay mode (810); and the first core network element sends an SIP registration response message corresponding to the SIP registration request message to the remote terminal device (820). According to the method, SIP registration of the remote terminal equipment is realized aiming at a relay scene, so that the service data of the remote terminal equipment can be successfully transmitted, and the reliability of service transmission (such as emergency service or other services) aiming at the remote terminal equipment is improved.

Description

[0001] This application is a divisional application of the invention patent application with application number 202280094109.9 filed on May 6, 2022, and invention name “Wireless communication method, device, equipment, storage medium and program product”. Technical Field

[0002] The embodiments of the present application relate to the field of communication technology, and in particular, to a wireless communication method, apparatus, device, storage medium, and program product. Background Art

[0003] 3GPP (3rd Generation Partnership Project) introduced the NCIS (Network Controlled Interactive Services) service in the 5G (5th-Generation) NR (New Radio) system.

[0004] As a new service form, NCIS service is introduced into the standard for related standardized services. NCIS service is mainly aimed at applications such as AR (Augmented Reality), VR (Virtual Reality), and games, and has high requirements for service quality such as rate, latency, packet loss rate, and high-speed encoding and decoding. Therefore, further research is needed for NCIS service. Summary of the invention

[0005] The embodiments of the present application provide a wireless communication method, apparatus, device, storage medium and program product. The technical solution is as follows:

[0006] According to one aspect of an embodiment of the present application, a wireless communication method is provided, the method being performed by a first core network element in a network, the method comprising:

[0007] receiving a SIP (Session Initiation Protocol) registration request message from a remote terminal device, the remote terminal device accessing the network through a relay terminal device, the SIP registration request message being sent by the remote terminal device to the first core network element through the relay terminal device, the SIP registration request message including first information, the first information being used to indicate that the remote terminal device accesses the network through a relay;

[0008] Sending a SIP registration response message corresponding to the SIP registration request message to the remote terminal device.

[0009] According to another aspect of an embodiment of the present application, a wireless communication method is provided, the method being executed by a remote terminal device, the remote terminal device accessing a network through a relay terminal device, the method comprising:

[0010] Sending a SIP registration request message to the relay terminal device, wherein the SIP registration request message is sent by the relay terminal device to a first core network element in the network, and the SIP registration request message includes first information, and the first information is used to indicate that the remote terminal device accesses the network through a relay;

[0011] Receive a SIP registration response message corresponding to the SIP registration request message from the first core network network element.

[0012] According to another aspect of an embodiment of the present application, a wireless communication method is provided, the method being performed by a relay terminal device, the method comprising:

[0013] Receive a SIP registration request message sent by a remote terminal device;

[0014] Sending the SIP registration request message to the first core network element, wherein the SIP registration request message includes first information, and the first information is used to indicate that the remote terminal device accesses the network through a relay;

[0015] Receiving a SIP registration response message corresponding to the SIP registration request message from the first core network network element;

[0016] Send the SIP registration response message to the remote terminal device.

[0017] According to another aspect of an embodiment of the present application, a wireless communication method is provided, the method being performed by a second core network element in a network, the method comprising:

[0018] Receiving a first request message sent by a first core network network element, wherein the first request message is used to request to obtain identity information of a remote terminal device; wherein the remote terminal device accesses the network through a relay terminal device;

[0019] The identity information of the remote terminal device is sent to the first core network network element so that the first core network network element can authenticate the identity of the remote terminal device to determine whether to accept a SIP registration request message initiated by the remote terminal device.

[0020] According to another aspect of an embodiment of the present application, a wireless communication method is provided, the method being performed by a third core network element in a network, the method comprising:

[0021] Receiving report information sent by a relay terminal device, the report information including device information of a remote terminal device; wherein the remote terminal device accesses the network through the relay terminal device;

[0022] Sending a second request message to a fourth core network network element, where the second request message is used to request to obtain the identity information of the remote terminal device, and the second request message includes device information of the remote terminal device;

[0023] receiving a second response message from the fourth core network element, wherein the second response message includes identity information of the remote terminal device;

[0024] The identity information of the remote terminal device is sent to the second core network network element, and the identity information of the remote terminal device is used to provide to the first core network network element to authenticate the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0025] According to another aspect of an embodiment of the present application, a wireless communication method is provided, the method being performed by a fourth core network element in a network, the method comprising:

[0026] receiving a second request message sent by a third core network network element, wherein the second request message is used to request to obtain identity information of a remote terminal device, and the second request message includes device information of the remote terminal device; wherein the remote terminal device accesses the network through a relay terminal device;

[0027] A second response message is sent to the third core network network element, wherein the second response message includes the identity information of the remote terminal device; wherein the identity information of the remote terminal device is used to provide the first core network network element to authenticate the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0028] According to one aspect of an embodiment of the present application, a wireless communication device is provided, the device comprising:

[0029] A receiving module, configured to receive a SIP registration request message from a remote terminal device, wherein the remote terminal device accesses the network via a relay terminal device, wherein the SIP registration request message is sent by the remote terminal device to the first core network element via the relay terminal device, wherein the SIP registration request message includes first information, wherein the first information is used to indicate that the remote terminal device accesses the network via a relay;

[0030] The sending module is used to send a SIP registration response message corresponding to the SIP registration request message to the remote terminal device.

[0031] According to another aspect of an embodiment of the present application, a wireless communication device is provided, the device comprising:

[0032] A sending module, configured to send a SIP registration request message to a relay terminal device, wherein the SIP registration request message is sent by the relay terminal device to a first core network element in the network, and the SIP registration request message includes first information, wherein the first information is used to instruct the remote terminal device to access the network via a relay;

[0033] The receiving module is used to receive a SIP registration response message corresponding to the SIP registration request message from the first core network network element.

[0034] According to another aspect of an embodiment of the present application, a wireless communication device is provided, the device comprising:

[0035] A receiving module, used for receiving a SIP registration request message sent by a remote terminal device;

[0036] A sending module, configured to send the SIP registration request message to a first core network element, wherein the SIP registration request message includes first information, and the first information is used to instruct the remote terminal device to access the network through a relay;

[0037] The receiving module is further configured to receive a SIP registration response message corresponding to the SIP registration request message from the first core network network element;

[0038] The sending module is further used to send the SIP registration response message to the remote terminal device.

[0039] According to another aspect of an embodiment of the present application, a wireless communication device is provided, the device comprising:

[0040] A receiving module, configured to receive a first request message sent by a first core network element, wherein the first request message is used to request to obtain identity information of a remote terminal device; wherein the remote terminal device accesses the network through a relay terminal device;

[0041] The sending module is used to send the identity information of the remote terminal device to the first core network network element, so that the first core network network element can authenticate the identity of the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0042] According to another aspect of an embodiment of the present application, a wireless communication device is provided, the device comprising:

[0043] A receiving module, configured to receive report information sent by a relay terminal device, wherein the report information includes device information of a remote terminal device; wherein the remote terminal device accesses the network through the relay terminal device;

[0044] A sending module, configured to send a second request message to a fourth core network network element, wherein the second request message is used to request to obtain the identity information of the remote terminal device, and the second request message includes device information of the remote terminal device;

[0045] The receiving module is further configured to receive a second response message from the fourth core network element, wherein the second response message includes the identity information of the remote terminal device;

[0046] The sending module is also used to send the identity information of the remote terminal device to the second core network network element, and the identity information of the remote terminal device is used to provide the first core network network element to authenticate the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0047] According to another aspect of an embodiment of the present application, a wireless communication device is provided, the device comprising:

[0048] A receiving module, configured to receive a second request message sent by a third core network network element, wherein the second request message is used to request to obtain identity information of a remote terminal device, and the second request message includes device information of the remote terminal device; wherein the remote terminal device accesses the network through a relay terminal device;

[0049] A sending module is used to send a second response message to the third core network network element, wherein the second response message includes the identity information of the remote terminal device; wherein the identity information of the remote terminal device is used to provide the first core network network element to authenticate the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0050] According to one aspect of an embodiment of the present application, a communication device is provided, comprising a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the wireless communication method on the first core network network element side, or the wireless communication method on the remote terminal device side, or the wireless communication method on the relay terminal device side, or the wireless communication method on the second core network network element side, or the wireless communication method on the third core network network element side, or the wireless communication method on the fourth core network network element side.

[0051] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, and the computer program is used to be executed by a processor to implement the wireless communication method on the first core network network element side, or the wireless communication method on the remote terminal device side, or the wireless communication method on the relay terminal device side, or the wireless communication method on the second core network network element side, or the wireless communication method on the third core network network element side, or the wireless communication method on the fourth core network network element side.

[0052] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the wireless communication method on the first core network network element side, or the wireless communication method on the remote terminal device side, or the wireless communication method on the relay terminal device side, or the wireless communication method on the second core network network element side, or the wireless communication method on the third core network network element side, or the wireless communication method on the fourth core network network element side.

[0053] According to one aspect of an embodiment of the present application, a computer program product is provided, the computer program product comprising computer instructions, the computer instructions being stored in a computer-readable storage medium, the processor reading and executing the computer instructions from the computer-readable storage medium to implement the wireless communication method on the first core network network element side, or the wireless communication method on the remote terminal device side, or the wireless communication method on the relay terminal device side, or the wireless communication method on the second core network network element side, or the wireless communication method on the third core network network element side, or the wireless communication method on the fourth core network network element side.

[0054] The technical solution provided by the embodiments of the present application may have the following beneficial effects:

[0055] For the relay scenario, SIP registration of the remote terminal device is implemented, thereby ensuring that the business data of the remote terminal device can be successfully transmitted, and improving the reliability of business transmission (such as emergency business or other business) for the remote terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0057] Figure 2 is a schematic diagram of a 5G system architecture provided by an embodiment of the present application;

[0058] Figure 3 is a schematic diagram of a 5G system architecture provided by another embodiment of the present application;

[0059] Figure 4 is a schematic diagram of a 5G system architecture provided by another embodiment of the present application;

[0060] Figure 5 is a flowchart of a wireless communication method provided by an embodiment of the present application;

[0061] Figure 6 is a schematic diagram of a network architecture provided by another embodiment of the present application;

[0062] Figure 7 is a flowchart of a wireless communication method provided by another embodiment of the present application;

[0063] Figure 8 is a flowchart of a wireless communication method provided by another embodiment of the present application;

[0064] Fig. 9 It is a schematic diagram of a computer network OSI (Open System Interconnection) reference model provided by an embodiment of the present application;

[0065] Fig.10 is a flowchart of a wireless communication method provided by another embodiment of the present application;

[0066] Fig.11 is a flowchart of a wireless communication method provided by another embodiment of the present application;

[0067] Fig.12 is a flowchart of a wireless communication method provided by another embodiment of the present application;

[0068] Fig.13 is a block diagram of a wireless communication device provided by an embodiment of the present application;

[0069] Fig.14 is a block diagram of a wireless communication device provided by another embodiment of the present application;

[0070] Fig.15 is a block diagram of a wireless communication device provided by another embodiment of the present application;

[0071] Fig.16 is a block diagram of a wireless communication device provided by another embodiment of the present application;

[0072] Fig.17 is a block diagram of a wireless communication device provided by another embodiment of the present application;

[0073] Fig.18 is a block diagram of a wireless communication device provided by another embodiment of the present application;

[0074] Fig.19 is a schematic diagram of the structure of a terminal device provided by an embodiment of the present application;

[0075] Fig. 20 It is a structural diagram of a core network element provided by an embodiment of the present application. DETAILED DESCRIPTION

[0076] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0077] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0078] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), fifth generation communication system or other communication systems, etc.

[0079] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0080] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0081] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0082] The embodiments of the present application may be applied to non-terrestrial communication networks (NTN) systems, and may also be applied to terrestrial communication networks (TN) systems.

[0083] Please refer to Figure 1 , which shows a schematic diagram of a network architecture provided by an embodiment of the present application. The network architecture may include: a terminal device 10, an access network device 20 and a core network element 30.

[0084] The terminal device 10 may refer to UE (User Equipment), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent or user device. In some embodiments, the terminal device 10 may also be a cellular phone, a cordless phone, a SIP phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with wireless communication function, a computing device or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in 5GS or a terminal device in a future evolved PLMN (Public Land Mobile Network), etc., which is not limited in the embodiments of the present application. For the convenience of description, the above-mentioned devices are collectively referred to as terminal devices. The number of terminal devices 10 is usually multiple, and one or more terminal devices 10 may be distributed in a cell managed by each access network device 20. In the embodiments of the present application, "terminal device" and "UE" are usually mixed, but those skilled in the art can understand their meanings.

[0085] The access network device 20 is a device deployed in the access network to provide wireless communication functions for the terminal device 10. The access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems using different wireless access technologies, the names of devices with access network device functions may be different, for example, in the 5G NR system, they are called gNodeB or gNB. With the evolution of communication technology, the name "access network device" may change. For the convenience of description, in the embodiment of the present application, the above-mentioned devices that provide wireless communication functions for the terminal device 10 are collectively referred to as access network devices. In some embodiments, a communication relationship can be established between the terminal device 10 and the core network element 30 through the access network device 20. Exemplarily, in an LTE (Long Term Evolution) system, the access network device 20 may be one or more eNodeBs in EUTRAN (Evolved Universal Terrestrial Radio Access Network) or EUTRAN; in a 5G NR system, the access network device 20 may be one or more gNBs in RAN (Radio Access Network) or RAN.

[0086] The core network element 30 is a network element deployed in the core network. The function of the core network element 30 is mainly to provide user connection, user management, and service bearing, and to provide an interface to the external network as a bearer network. For example, the core network elements in the 5G NR system may include network elements such as AMF (Access and Mobility Management Function), UPF (User Plane Function), and SMF (Session Management Function). In addition, the core network element can be regarded as a functional entity, and one or more core network elements can be deployed on a physical device.

[0087] In some embodiments, the access network device 20 and the core network element 30 communicate with each other through some air interface technology, such as the NG interface in the 5G NR system. The access network device 20 and the terminal device 10 communicate with each other through some air interface technology, such as the Uu interface.

[0088] The "5G NR system" in the embodiment of the present application may also be referred to as a 5G system or an NR system, but those skilled in the art may understand its meaning. The technical solution described in the embodiment of the present application may be applicable to an LTE system, a 5G NR system, a subsequent evolution system of the 5G NR system, or other communication systems such as an NB-IoT (Narrow Band Internet of Things) system, and the present application does not limit this.

[0089] In an embodiment of the present application, the access network device can provide services for the cell, and the terminal device communicates with the access network device through the transmission resources (for example, frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be a cell corresponding to the access network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cell, microcell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0090] Please refer to Figure 2 , which shows a schematic diagram of the system architecture of the 5GS (5th Generation System, fifth generation mobile communication system) provided in the embodiment of the present application. Figure 2As shown, the system architecture 200 may include: UE (also known as the "terminal equipment" introduced above), (R)AN ((Radio)Access Network), Core (core network) and DN (Data Network). Among them, UE, (R)AN, Core are the main components of the architecture. Logically, they can be divided into two parts: the user plane and the control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data. In the figure, the NG2 reference point is located between the (R)AN control plane and the Core control plane, the NG3 reference point is located between the (R)AN user plane and the Core user plane, and the NG6 reference point is located between the Core user plane and the data network.

[0091] UE: It is the entry point for mobile users to interact with the network. It can provide basic computing and storage capabilities, display service windows to users, and receive user operation input. UE will use the next generation air interface technology to establish signal and data connections with (R)AN, thereby transmitting control signals and service data to the mobile network.

[0092] (R)AN: Similar to the base station in the traditional network, it is deployed close to the UE to provide network access for authorized users in a specific area and can use transmission tunnels of different qualities to transmit user data according to the user level and business requirements. (R)AN can manage its own resources, use them reasonably, provide access services to UE on demand, and forward control signals and user data between UE and the core network.

[0093] Core: Responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing UE with functions such as session management, mobility management, policy management, and security authentication. When the UE registers, it provides the UE with network access authentication; when the UE has a service request, it allocates network resources to the UE; when the UE moves, it updates the network resources for the UE; when the UE is idle, it provides the UE with a fast recovery mechanism; when the UE deregisters, it releases network resources for the UE; when the UE has service data, it provides the UE with data routing functions, such as forwarding uplink data to the DN; or receiving UE downlink data from the DN and forwarding it to the (R)AN, and then sending it to the UE.

[0094] DN: It is a data network that provides business services to users. Generally, the client is located in the UE and the server is located in the data network. The data network can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet, or a proprietary network jointly deployed by operators, such as for configuring IMS (IP Multimedia Subsystem) services.

[0095] Figure 3is Figure 2 The detailed architecture is determined on the basis of the core network, in which the core network user plane includes UPF; the core network control plane includes AUSF (Authentication Server Function), AMF, SMF, NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), PCF (Policy Control Function), and AF (Application Function).

[0096] exist Figure 3 In the architecture shown, the UE establishes an AS (Access Stratum) connection with the (R)AN through the Uu port, exchanges AS messages and wireless data transmission, and the UE establishes an NAS (Non Access Stratum) connection with the AMF through the N1 port, exchanges NAS messages. AMF is the mobility management function in the core network, and SMF is the session management function in the core network. In addition to mobility management of the UE, AMF is also responsible for forwarding session management related messages between the UE and SMF. PCF is the policy management function in the core network, responsible for formulating policies related to mobility management, session management, and billing of the UE. UPF is the user plane function in the core network, which transmits data with the external data network through the N6 interface and with the (R)AN through the N3 interface.

[0097] It should be noted that Figure 2 and Figure 3 The interface name between the various network elements is only an example. The name of the interface in a specific implementation may be other names, and the embodiments of the present application do not specifically limit this. Figure 2 and Figure 3The names of the various network elements (such as SMF, AF, UPF, etc.) included in are only examples and do not limit the functions of the network elements themselves. In 5GS and other future networks, the above-mentioned network elements may also have other names, and the embodiments of the present application do not specifically limit this. For example, in a 6G network, some or all of the above-mentioned network elements may use the terminology in 5G, or may use other names, etc., which are uniformly explained here and will not be repeated below. In addition, it should be understood that the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.

[0098] Before introducing the technical solution of this application, some background technical knowledge involved in this application is first introduced and explained. The following related technologies can be combined arbitrarily with the technical solution of the embodiment of this application as optional solutions, and they all belong to the protection scope of the embodiment of this application. The embodiment of this application includes at least part of the following contents.

[0099] Please refer to Figure 4 , which shows a schematic diagram of the 5G system architecture provided by the embodiment of the present application. Figure 4 As shown, the terminal device accesses the data network to use IMS services. The system architecture 200 may include: UE (also known as the "terminal device" introduced above), access network equipment, AMF, SMF and UPF, UDM, Home Subscriber Server (HSS), PCF, Proxy Call Session Control Function (P-CSCF), Serving Call Session Control Function (S-CSCF), technology-related RFS (TAS), Interconnection Border Control Function (IBCF), Border Gateway Control Function (BGCF), Media Gateway Control Function (MGCF) + Media Plane Function, Part B.

[0100] In a possible embodiment, the UDM / HSS can be connected to the TAS through the Sh interface, the TAS can be connected to the S-CSCF through the ISC interface, the UDM / HSS can be connected to the S-CSCF through the Cx interface, the H-PCF can be connected to the P-CSCF through the Rx or N5 interface, the P-CSCF can be connected to the S-CSCF through the Mw, and the UOF of the home network can be connected to the interconnection border control function network element (IBCF) / border gateway control function network element (BGCF) / media gateway control function network element (MGCF) + media plane function network element through the N6 interface. In addition, Figure 4 In the example, the control plane can be Figure 3 The dotted line shown passes through the P-CSCF and the S-CSCF, and the media plane may be a dotted line that does not pass through the P-CSCF and the S-CSCF.

[0101] Please refer to Figure 5 , which shows a flow chart of a wireless communication method provided by an embodiment of the present application. The method can be applied to Figure 1 In the network architecture shown in FIG. 1 , the method may include at least one of the following steps (A1 to A11):

[0102] Step A1: The terminal device is registered in the data network.

[0103] Step A2: The terminal device sends a PDU (Protocol Data Unit) session establishment request (urgent) to AMF.

[0104] The UE sends a UL NAS Transport message to the AMF, which includes the request type (set to initial emergency request), PDU Session ID (PDU Session Identity), and PDU session Establishment Request message.

[0105] Step A3, AMF obtains the GPSI (Generic Public Subscription Identifier, which is equivalent to the MSISDN (Mobile Station ISDN number) of 4G (4th-Generation)) of the terminal device from UDM (GPSI here is MSISDN).

[0106] Step A4, AMF sends Nsmf_PDUSession_CreateSMContextRequest to SMF.

[0107] The message carries PDU session ID, DNN (Data Network Name), S-NSSAI (Single-Network Slice Selection Assistance Information), request type, SUPI (SUbscription Permanent Identifier), PEI (Permanent Equipment Identifier), and GPSI.

[0108] Step A5, SMF sends Npcf_SMPolicyControl_Create to PCF, and sends the SUPI, PEI, and GPSI of the terminal device to PCF.

[0109] Step A6, SMF receives the PDU session establishment request message and sends Namf_Communication_N1N2MessageTransfer to AMF.

[0110] The message includes a PDU session establishment Accept message, which includes a QoS rule (Quality of Service rule), QoS flow parameters, DNN, S-NSSAI, and PCO (Protocol Configuration Option). PCO may carry the address or FQDN (Fully Qualified Domain Name) of P-CSCF (Proxy Call Session Control Function). If PCO does not carry the address of P-CSCF, the UE may use the pre-configured P-CSCF address or use DHCP (Dynamic Host Configuration Protocol) to obtain the P-CSCF address.

[0111] Step A7: AMF sends a DL NAS Transport message to the UE, which includes a PDU session establishment acceptance message and a PDU session identifier.

[0112] Step A8: The UE sends a SIP registration message to the P-CSCF. The message includes a user ID (user identification), and the user ID is IMS Private User Identity (IMPI).

[0113] Step A9-10: P-CSCF obtains SUPI, IMEI (International Mobile Equipment Identity), and GPSI from PCF according to UE IP (Internet Protocol) address.

[0114] Step A11: The P-CSCF returns a SIP registration response message to the terminal device.

[0115] In 3GPP R17, the 5G ProSe (Proximity Service) project is used to design solutions for proximity service communications. ProSe includes NCIS. One of the important scenarios of Prose is the UE-to-network (U2N) relay scenario. U2N relay is to relay data for remote UE (remote terminal device) through a relay UE (relay terminal device), so that remote UE (remote terminal device) can communicate with the network. Please refer to Figure 6 , which shows a schematic diagram of a system architecture for transmitting data from a remote terminal device to a data network through a relay terminal device provided in an embodiment of the present application. Figure 6 As shown in the figure, a PC5 link is established between the remote terminal device (Remote UE) and the relay terminal device (Relay UE), and the relay terminal device uses the PDU session to relay the data from the remote terminal device to the remote terminal device. Because each PDU session has a type, for example: IPv4 (Internet Protocol version 4), IPv6 (Internet Protocol version 6), Ethernet, Unstructured. Only data of this type can be transmitted using the corresponding PDU session. Figure 6In the architecture diagram, the remote terminal device does not have its own core network elements (such as SMF, UPF, PCF, AMF). In order to realize relay communication, the relay terminal device and the remote terminal device need to obtain necessary configuration parameters before relay communication. These configuration parameters can come from PCF, application server, pre-configured on the terminal or SIM (Subscriber Identity Module) card. Before transmitting data, the remote terminal device needs to find a suitable relay terminal device and establish a PC5 connection with it.

[0116] In the embodiment of the present application, the PC5 interface is a D2D (Device-to-Device) interface. PC5 is a direct communication interface, a communication interface between terminals, that is, a short-distance direct communication interface between vehicles, people, and road infrastructure; its characteristics are: low-latency, high-capacity, and highly reliable communication is achieved through direct connection, broadcasting, and network scheduling.

[0117] Please refer to Figure 7 , which shows a flowchart of a remote terminal device accessing a data network provided by an embodiment of the present application. The method can be applied to Figure 6 In the system architecture shown in FIG. 1 , the method may include at least one of the following steps (B1 to B10):

[0118] Step B1: Authorize and configure the L3 (Layer-3) relay terminal device through the data network.

[0119] Step B2: Authorize and configure the L3 remote terminal device through the data network.

[0120] Step B3: Establish a PDU session between the relay terminal device and the data network.

[0121] Before the connection between the relay terminal device and the remote terminal device is established, a PDU session is first established to relay subsequent data.

[0122] Step B4, remote terminal device discovery process.

[0123] The remote terminal device performs a discovery process to discover a relay terminal device that meets the needs of the remote terminal device. In this process, the remote terminal device learns the connection services that the relay terminal device can provide.

[0124] Step B5: establishing a communication connection between the remote terminal device and the relay terminal device.

[0125] The remote terminal device selects a relay terminal device and establishes a connection with the relay terminal device.

[0126] Step B6: The relay terminal device establishes a new PDU session in the data network.

[0127] If there is no established PDU session that meets the requirements, before completing the PC5 connection establishment, the relay terminal device initiates a new PDU session establishment process to the network.

[0128] Step B7: The relay terminal device allocates an IP address / prefix to the remote terminal device.

[0129] For IP-type PDU sessions and IP traffic on the PC5 interface, the corresponding IP address is assigned to the remote terminal device.

[0130] Step B8, L2 (Layer-2, Layer 2) link modification.

[0131] The remote terminal device may provide the relay terminal device with QoS info (quality of service information) of PC5 in the L2 link modification process. The relay terminal device determines new QoS (Quality of Service) parameters based on the QoS info (quality of service information) of PC5 and initiates the PDU session modification process.

[0132] Step B9: The relay terminal device modifies the existing PDU session for relaying.

[0133] Step B10: The relay terminal device sends a remote terminal device report (including a remote terminal device identifier (RemoteUser ID) and remote terminal device information (RemoteUE info)).

[0134] The remote terminal device identifies the remote terminal device that successfully establishes a connection in step B5. The remote terminal device information is an auxiliary identifier used to identify the type of PDU session established through the relay. For example, for an IP type PDU session, it is the IP information of the remote terminal device (Remote UE IP info).

[0135] In the above embodiment, a SIP registration process is provided for non-relay scenarios, but no SIP registration process is provided for relay scenarios. Therefore, the embodiment of the present application provides a technical solution, which provides a SIP registration process for a remote terminal device for a relay scenario, so as to ensure that the service data of the remote terminal device can be successfully transmitted, thereby improving the reliability of service transmission (such as emergency services or other services) for the remote terminal device.

[0136] Please refer to Figure 8 , which shows a flow chart of a wireless communication method provided by an embodiment of the present application. The method can be applied to Figure 1Or the network architecture shown in 6. The method may include at least one of the following steps (810-820):

[0137] Step 810: The remote terminal device sends a SIP registration request message to a first core network element in the network through a relay terminal device, wherein the SIP registration request message includes first information, and the first information is used to indicate that the remote terminal device accesses the network through a relay.

[0138] The remote terminal device accesses the network through the relay terminal device, and the SIP registration request message is sent by the remote terminal device to the first core network network element through the relay terminal device. After receiving the SIP registration request message sent by the remote terminal device, the relay terminal device sends the SIP registration request message to the first core network network element. Correspondingly, the first core network network element receives the SIP registration request message from the remote terminal device.

[0139] The SIP registration request message is a message for SIP registration sent by a terminal device to a core network element. In an embodiment of the present application, for a relay scenario, a remote terminal device sends a SIP registration request message to a first core network element through a relay terminal device, and the SIP registration request message includes first information, which indicates that the remote terminal device accesses the network through a relay mode, so as to distinguish it from a SIP registration request message initiated in a non-relay mode.

[0140] In some embodiments, the SIP registration request message further includes second information, and the second information is used to indicate the identity information of the remote terminal device. In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI (SUbscription Concealed Identifier), PEI, GPSI, MSISDN.

[0141] In some embodiments, the relay mode is a layer 3 (Layer-3, referred to as L3) relay mode, and the first information is used to indicate that the remote terminal device accesses the network through the layer 3 relay mode. Fig. 9, which shows a schematic diagram of the computer network OSI reference model. In the computer network OSI reference model 900, the layer 1 relay mode refers to the relay of the physical layer. The physical layer relay is the lowest layer in the computer network OSI reference model. It provides mechanical, electronic, functional and standardized characteristics for the creation, maintenance and removal of the physical link required for data transmission. The transmission of the physical layer ensures that the original data can be transmitted on various physical media. The layer 2 relay mode refers to the relay of the data link layer. The data link layer is the second layer in the computer network OSI reference model, between the physical layer and the network layer. The data link layer provides services to the network layer on the basis of the services provided by the physical layer. The most basic service is to reliably transmit data from the network layer to the target machine network layer of the adjacent node. Layer 3 relay mode refers to relaying at the network layer. The network layer is the third layer of the OSI reference model of computer networks, between the transport layer and the data link layer. It further manages data communications in the network based on the data frame transmission function between two adjacent endpoints provided by the data link layer, and tries to transmit data from the source to the destination through several intermediate nodes, thereby providing the most basic end-to-end data transmission service to the transport layer. This application proposes a technical solution for remote terminal devices to implement SIP registration for L3 relay scenarios.

[0142] Step 820: The first core network element sends a SIP registration response message corresponding to the SIP registration request message to the remote terminal device.

[0143] In some embodiments, the first core network network element sends a SIP registration response message corresponding to the SIP registration request message to the remote terminal device through the relay terminal device. The relay terminal device receives the SIP registration response message corresponding to the SIP registration request message from the first core network network element, and sends the SIP registration response message to the remote terminal device. Correspondingly, the remote terminal device receives the SIP registration response message from the first core network network element from the relay terminal device. In some embodiments, the SIP registration response message is used to indicate that the remote terminal device has successfully registered with the SIP.

[0144] In some embodiments, the first core network element is obtained by the remote terminal device through a DHCP request; or, the first core network element is pre-configured. In some embodiments, the first core network element is a P-CSCF.

[0145] The technical solution provided in the embodiment of the present application realizes SIP registration of remote terminal devices for relay scenarios, thereby ensuring that the business data of the remote terminal devices can be successfully transmitted, and improving the reliability of business transmission (such as emergency business or other business) for the remote terminal devices.

[0146] In some embodiments, when it is determined according to the first information that the SIP registration request message is initiated by the remote terminal device through a relay mode, the first core network network element does not execute the identity authentication process for the remote terminal device, and directly sends the SIP registration response message to the remote terminal device. That is, the SIP registration response message is directly sent by the first core network network element without executing the identity authentication process for the remote terminal device when it is determined according to the first information that the remote terminal device is initiated through a relay mode. In some embodiments, the relay mode is a layer 3 relay mode.

[0147] The technical solution provided in the embodiment of the present application sends a SIP registration request message initiated by a remote terminal device to a first core network network element through a relay terminal device. The first core network network element can directly send a SIP registration response message corresponding to the SIP registration request message to the remote terminal device. For the relay scenario, a simplified SIP registration process is provided, that is, the first core network network element does not need to authenticate the identity of the remote terminal device, and directly confirms that its registration is successful. This implementation method is relatively simple and efficient.

[0148] Of course, in addition to providing a simplified SIP registration process, the technical solution provided by the embodiment of the present application also provides a SIP registration process for identity authentication of remote terminal devices and registration after the identity authentication is passed in order to improve the security of SIP registration in the relay scenario and avoid SIP registration by some illegal or malicious terminal devices.

[0149] Please refer to Fig.10 , which shows a flow chart of a wireless communication method provided by another embodiment of the present application. The method can be applied to Figure 1 Or the network architecture shown in 6. The method may include at least one of the following steps (1010-1040):

[0150] Step 1010: The remote terminal device sends a SIP registration request message to the first core network element.

[0151] In some embodiments, the remote terminal device sends a SIP registration request message to the first core network element in the network through the relay terminal device.

[0152] In some embodiments, the SIP registration request message includes second information, where the second information is used to indicate identity information of the remote terminal device.

[0153] In some embodiments, the SIP registration request message includes first information and second information; wherein the first information is used to indicate that the remote terminal device accesses the network via a relay method, to distinguish it from a SIP registration request message initiated in a non-relay method, and the second information is used to indicate the identity information of the remote terminal device.

[0154] The identity information of the remote terminal device is used to characterize the identity of the remote terminal device. In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI, PEI, GPSI, MSISDN. That is, the second information is used to indicate at least one of the following identity information of the remote terminal device: IMPI, SUPI, SUCI, PEI, GPSI, MSISDN.

[0155] In some embodiments, the first core network element is obtained by the remote terminal device through a DHCP request; or, the first core network element is pre-configured. In some embodiments, the first core network element is a P-CSCF.

[0156] In some embodiments, the above relay method is a layer 3 (Layer-3) relay method.

[0157] Step 1020: The first core network element sends a first request message to the second core network element, where the first request message is used to request identity information of a remote terminal device.

[0158] Correspondingly, the second core network network element receives the first request message sent by the first core network network element.

[0159] In some embodiments, the first request message includes the IP address, port number and third information of the remote terminal device, and the third information is used to indicate the acquisition of the identity information of the remote terminal device. After receiving the first request message, the second core network network element acquires the identity information of the remote terminal device according to the first request message. For example, the second core network network element determines that the request is for acquiring the identity information of the remote terminal device based on the third information carried in the first request message, and then acquires the identity information of the remote terminal device from the stored mapping information based on the IP address and port number of the remote terminal device carried in the request. The mapping information includes a mapping relationship between the IP address and port number of at least one terminal device and the identity information.

[0160] In some embodiments, the second core network element is a PCF of the relay terminal device. That is, the first core network element sends a first request message to the PCF of the relay terminal device, and the first request message is used to request to obtain the identity information of the remote terminal device.

[0161] Step 1030: The second core network element sends the identity information of the remote terminal device to the first core network element.

[0162] After receiving the identity information of the remote terminal device sent by the second core network element, the first core network element detects whether the identity information of the remote terminal device indicated in the SIP registration request message is consistent with the identity information of the remote terminal device obtained from the second core network element. If the detection result is consistent, the following step 1040 is executed.

[0163] Step 1040: The first core network element sends a SIP registration response message corresponding to the SIP registration request message to the remote terminal device.

[0164] In some embodiments, the SIP registration response message is used to indicate that the SIP registration of the remote terminal device is successful.

[0165] In some embodiments, if the detection result is inconsistent, step 1040 is not executed, that is, the first core network network element does not send a SIP registration response message corresponding to the SIP registration request message to the remote terminal device, or sends a SIP registration failure message corresponding to the SIP registration request message to the remote terminal device, and the SIP registration failure message is used to indicate that the SIP registration of the remote terminal device has failed.

[0166] In the technical solution provided by the embodiment of the present application, the first core network network element can also perform identity authentication for the remote terminal device. When it is detected that the identity information of the remote terminal device indicated in the SIP registration request message is consistent with the identity information of the remote terminal device obtained from the second core network network element, a SIP registration response message corresponding to the SIP registration request message is sent to the remote terminal device. By authenticating the remote terminal device, the security of SIP registration in the relay scenario is improved, and some illegal or malicious terminal devices are prevented from performing SIP registration.

[0167] Please refer to Fig.11 , which shows a flow chart of a wireless communication method provided by another embodiment of the present application. The method can be applied to Figure 1 Or the network architecture shown in 6. The method may include at least one of the following steps (S1-S9):

[0168] Step S1. PCF authorizes and configures the layer 3 relay terminal device.

[0169] In some embodiments, the PCF configures the following parameters to the relay terminal device:

[0170] - PLMN ID (Public Land Mobile Network) of the UE allowed to act as a relay;

[0171] -Relay discovery strategy and parameters, including:

[0172] ■U2N Relay discovery parameters: User Info ID, Relay Service Code(s);

[0173] ■Default destination Layer-2 ID for sending and receiving U2N discovery messages;

[0174] ■PDU session parameters corresponding to the Relay Service code: PDUSession type, DNN, SSC Mode, S-NSSAI;

[0175] ■Relay Service code that can provide emergency services.

[0176] Step S2. PCF authorizes and configures the layer 3 remote terminal device.

[0177] In some embodiments, the PCF configures the following parameters to the remote terminal device:

[0178] -Whether it is allowed to act as a remote UE (remote terminal equipment);

[0179] -Relay discovery strategy and parameters, including:

[0180] ■U2N Relay discovery parameters: User Info ID (user information identifier), Relay Service Code (s) (relay service code);

[0181] ■Default destination Layer-2 ID for sending and receiving U2N discovery messages;

[0182] ■PDU session parameters corresponding to the Relay Service code: PDUSession type, DNN, SSC Mode, S-NSSAI;

[0183] ■Relay Service code that can provide emergency services.

[0184] Step S3: Remote terminal device discovery process.

[0185] In some embodiments, the remote terminal device performs a discovery process, which may be a model A discovery process or a model B discovery process; the remote UE selects a suitable relay UE to serve it.

[0186] Step S4: Establish a PC5 link between the remote terminal device and the relay terminal device.

[0187] In some embodiments, the remote UE (remote terminal device) initiates a PC5 link establishment process to the relay UE (relay terminal device) to establish a unicast communication channel; during the PC5 link establishment process, the remote UE (remote terminal device) provides a relay service code to the relay UE (relay terminal device); here, because the remote UE (remote terminal device) wants to use emergency service, the relay service code also corresponds to the emergency service.

[0188] Step S5: The relay terminal device establishes an emergency PDU session.

[0189] In some embodiments, if the relay UE (relay terminal device) has not established an emergency PDU session (emergency PDU session), the relay UE (relay terminal device) initiates the establishment of an emergency PDU session (emergency PDU session).

[0190] Step S6. IP address allocation.

[0191] In some embodiments, the relay terminal device assigns an IP address to the remote terminal device.

[0192] Step S7. The relay terminal device sends report information to the SMF.

[0193] In some embodiments, the relay terminal device sends report information to the SMF (third core network element). The report information includes device information of the remote terminal device. The device information includes at least one of the following: SUPI, SUCI.

[0194] In some embodiments, the report information includes the SUCI or SUPI, IP address and port number of the remote UE (remote terminal equipment).

[0195] Step S8: The remote terminal device sends a SIP registration request message to the P-CSCF.

[0196] In some embodiments, the remote terminal device sends a SIP registration request message to the first core network element (P-CSCF).

[0197] In some embodiments, the remote UE (remote terminal equipment) performs P-CSCF discovery; the remote UE (remote terminal equipment) can use DHCP (Dynamic Host Configuration Protocol) request to perform P-CSCF discovery, or it can use a pre-configured P-CSCF; the remote UE (remote terminal equipment) sends a SIP registration request message to the P-CSCF, and the message carries a user ID, and the user ID is IMPI; the message may also carry SUPI, PEI, and MSISDN; the message also carries access via L3 relay, which is used to instruct the P-CSCF not to go to the PCF to obtain the SUPI, PEI and MSISDN of the remote UE (remote terminal equipment).

[0198] Step S9. The P-CSCF sends a SIP registration response message to the remote terminal device.

[0199] In some embodiments, the P-CSCF does not obtain the SUPI, PEI and MSISDN from the PCF, thus avoiding consistency checking; the P-CSCF returns a SIP registration response to the remote terminal device.

[0200] Please refer to Fig.12 , which shows a flow chart of a wireless communication method provided by another embodiment of the present application. The method can be applied to Figure 1 Or the network architecture shown in 6. The method may include at least one of the following steps (G1-G14):

[0201] Step G1. PCF authorizes and configures the layer 3 relay terminal device.

[0202] Step G2. PCF authorizes and configures the layer 3 remote terminal device.

[0203] Step G3: Remote terminal device discovery process.

[0204] Step G4. Establish a PC5 link between the remote terminal device and the relay terminal device.

[0205] Step G5. The relay terminal device establishes an emergency PDU session.

[0206] Step G6. IP address allocation.

[0207] Step G7. The relay terminal device sends report information to the SMF.

[0208] Steps G1 to G7 have been explained in detail in other embodiments of the present application, and steps G1 to G7 will not be repeated here.

[0209] Step G8. SMF sends a second request message to UDM.

[0210] The third core network element (SMF) sends a second request message to the fourth core network element (UDM), the second request message is used to request to obtain the identity information of the remote terminal device, and the second request message includes the device information of the remote terminal device. The second request message includes fourth information, and the fourth information is used to indicate to obtain the identity information of the remote terminal device.

[0211] The fourth core network network element (UDM) receives the second request message sent by the third core network network element (SMF).

[0212] In some embodiments, if the SMF of the relay UE (relay terminal device) obtains the SUPI of the remote UE (remote terminal device), the SMF sends a message Nudm_SDM_Get to the UDM of the remote UE (remote terminal device), and the message carries SUPI and GPSI acquisition instructions (fourth information); if the SMF obtains the SUCI of the remote UE (remote terminal device), the SMF sends a message Nudm_SDM_Get to the UDM of the remote UE (remote terminal device), and the message carries SUCI and GPSI acquisition instructions (fourth information).

[0213] Step G9. UDM sends a second response message to SMF.

[0214] The third core network element (SMF) receives a second response message from the fourth core network element (UDM), and the second response message includes identity information of the remote terminal device.

[0215] In some embodiments, the UDM returns the SUPI and GPSI (MSISDN) to the SMF of the relay UE (relay terminal equipment).

[0216] Step G10. SMF sends the identity information of the remote terminal device to PCF.

[0217] The third core network element (SMF) sends the identity information of the remote terminal device to the second core network element (PCF). The identity information of the remote terminal device is used to provide the first core network element with identity authentication of the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0218] In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI, PEI, GPSI, MSISDN.

[0219] In some embodiments, the SMF of the relay UE (relay terminal device) sends the SUPI, GPSI, and PEI of the remote UE (remote terminal device) to the PCF of the relay UE (relay terminal device) through the Npcf_SMPolicyControl_Update (NPCF session management policy control update) process.

[0220] Step G11. The remote terminal device sends a SIP registration request message to the P-CSCF.

[0221] In some embodiments, the remote UE (remote terminal equipment) performs P-CSCF discovery; the remote UE (remote terminal equipment) can use DHCP request to discover the P-CSCF, or use a pre-configured P-CSCF; the remote UE (remote terminal equipment) sends a SIP registration request message to the P-CSCF, and the message carries a user ID, and the user ID is IMPI; the message may also carry SUPI, PEI, MSISDN, and the message also carries access via L3 relay.

[0222] Step G12. The P-CSCF sends a first request message to the PCF.

[0223] In some embodiments, the P-CSCF obtains the information of the remote UE (remote terminal device) from the PCF of the relay UE (relay terminal device), and the P-CSCF sends an Npcf_PolicyAuthorization_Create Request (NPCF policy authorization creation request) message to the PCF of the relay UE (relay terminal device), carrying the UE IPaddress (terminal IP address, relay UE (relay terminal device), remote UE (remote terminal device) may use the same IP address), and the Port number (port number) reported by the remote UE (remote terminal device), to obtain the remote UE (remote terminal device) information indication.

[0224] Step G13. PCF sends a first response message to P-CSCF.

[0225] In some embodiments, the PCF of the relay UE returns an Npcf_PolicyAuthorization_Create Response (NPCF policy authorization creation response) message to the P-CSCF, and the message carries the SUPI, PEI, and MSISDN of the remote UE (remote terminal equipment).

[0226] Step G14. The P-CSCF sends a SIP registration response message to the remote terminal device.

[0227] In some embodiments, the P-CSCF decides to accept the registration request based on the information obtained in G13, and returns a SIP registration response message to the remote UE (remote terminal device).

[0228] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0229] Please refer to Fig.13 , which shows a block diagram of a wireless communication device provided by an embodiment of the present application. The device has the function of implementing the method example executed by the first core network element side, and the function can be implemented by hardware, or by hardware executing corresponding software. The device can be implemented as a first core network element, or as a part of a first core network element. Fig.13 As shown, the device 1300 may include: a receiving module 1310 and a sending module 1320 .

[0230] The receiving module 1310 is used to receive a SIP registration request message from a remote terminal device, where the remote terminal device accesses the network via a relay terminal device. The SIP registration request message is sent by the remote terminal device to the first core network element via the relay terminal device. The SIP registration request message includes first information, and the first information is used to indicate that the remote terminal device accesses the network via a relay.

[0231] The sending module 1320 is used to send a SIP registration response message corresponding to the SIP registration request message to the remote terminal device.

[0232] In some embodiments, the relay mode is a layer 3 relay mode.

[0233] In some embodiments, when it is determined based on the first information that the remote terminal device accesses the network via a relay, the first core network element does not perform an identity authentication process for the remote terminal device, and directly sends the SIP registration response message to the remote terminal device.

[0234] In some embodiments, the SIP registration request message further includes second information, where the second information is used to indicate identity information of the remote terminal device.

[0235] In some embodiments, the apparatus further includes a detection module 1330 and a determination module 1340 .

[0236] The detection module 1330 is used to detect whether the identity information of the remote terminal device indicated in the SIP registration request message is consistent with the identity information of the remote terminal device obtained from the second core network network element.

[0237] The determining module 1340 is used to determine to accept the SIP registration request message if they are consistent, and to execute the step of sending the SIP registration response message to the remote terminal device through the sending module 1320.

[0238] In some embodiments, the sending module 1320 is further used to send a first request message to the second core network element, where the first request message is used to request to obtain the identity information of the remote terminal device.

[0239] The receiving module 1310 is further configured to receive the identity information of the remote terminal device sent by the second core network element.

[0240] In some embodiments, the first request message includes the IP address, port number and third information of the remote terminal device, and the third information is used to indicate the acquisition of identity information of the remote terminal device.

[0241] In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI, PEI, GPSI, and MSISDN.

[0242] In some embodiments, the second core network element is the PCF of the relay terminal device.

[0243] In some embodiments, the first core network element is obtained by the remote terminal device through a DHCP request; or, the first core network element is pre-configured.

[0244] In some embodiments, the first core network element is a P-CSCF.

[0245] The technical solution provided in the embodiment of the present application realizes SIP registration of remote terminal devices for relay scenarios, thereby ensuring that the business data of the remote terminal devices can be successfully transmitted, and improving the reliability of business transmission (such as emergency business or other business) for the remote terminal devices.

[0246] Please refer to Fig.14 , which shows a block diagram of a wireless communication device provided by another embodiment of the present application. The device has the function of implementing the method example executed by the above-mentioned remote terminal device side, and the function can be implemented by hardware, or by hardware executing corresponding software. The device can be implemented as a remote terminal device, or implemented as a part of a remote terminal device. Fig.14 As shown, the device 1400 may include: a sending module 1410 and a receiving module 1420 .

[0247] The sending module 1410 is used to send a SIP registration request message to a relay terminal device. The SIP registration request message is sent by the relay terminal device to a first core network element in the network. The SIP registration request message includes first information, and the first information is used to indicate that the remote terminal device accesses the network via a relay.

[0248] The receiving module 1420 is configured to receive a SIP registration response message corresponding to the SIP registration request message from the first core network element.

[0249] In some embodiments, the relay mode is a layer 3 relay mode.

[0250] In some embodiments, the SIP registration response message is directly sent by the first core network element without executing an identity authentication process for the remote terminal device when it is determined based on the first information that the remote terminal device accesses the network via a relay.

[0251] In some embodiments, the SIP registration request message further includes second information, where the second information is used to indicate identity information of the remote terminal device.

[0252] In some embodiments, the SIP registration response message is sent by the first core network element when it is detected that the identity information of the remote terminal device indicated in the SIP registration request message is consistent with the identity information of the remote terminal device obtained from the second core network element.

[0253] In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI, PEI, GPSI, and MSISDN.

[0254] In some embodiments, the second core network element is the PCF of the relay terminal device.

[0255] In some embodiments, the first core network element is obtained by the remote terminal device through a DHCP request; or, the first core network element is pre-configured.

[0256] The technical solution provided in the embodiment of the present application realizes SIP registration of remote terminal devices for relay scenarios, thereby ensuring that the business data of the remote terminal devices can be successfully transmitted, and improving the reliability of business transmission (such as emergency business or other business) for the remote terminal devices.

[0257] Please refer to Fig.15 , which shows a block diagram of a wireless communication device provided by another embodiment of the present application. The device has the function of implementing the method example executed by the above-mentioned relay terminal device side, and the function can be implemented by hardware, or by hardware executing corresponding software. The device can be implemented as a relay terminal device, or implemented as a part of a relay terminal device. Fig.15 As shown, the device 1500 may include: a receiving module 1510 and a sending module 1520 .

[0258] The receiving module 1510 is used to receive a SIP registration request message sent by a remote terminal device.

[0259] The sending module 1520 is used to send the SIP registration request message to the first core network element, and the SIP registration request message includes first information, and the first information is used to instruct the remote terminal device to access the network through a relay.

[0260] The receiving module 1510 is further configured to receive a SIP registration response message corresponding to the SIP registration request message from the first core network element.

[0261] The sending module 1520 is further configured to send the SIP registration response message to the remote terminal device.

[0262] In some embodiments, the relay mode is a layer 3 relay mode.

[0263] In some embodiments, the SIP registration response message is directly sent by the first core network element without executing an identity authentication process for the remote terminal device when it is determined based on the first information that the remote terminal device accesses the network via a relay.

[0264] In some embodiments, the SIP registration request message further includes second information, where the second information is used to indicate identity information of the remote terminal device.

[0265] In some embodiments, the SIP registration response message is sent by the first core network element when it is detected that the identity information of the remote terminal device indicated in the SIP registration request message is consistent with the identity information of the remote terminal device obtained from the second core network element.

[0266] In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI, PEI, GPSI, and MSISDN.

[0267] The technical solution provided in the embodiment of the present application realizes SIP registration of remote terminal devices for relay scenarios, thereby ensuring that the business data of the remote terminal devices can be successfully transmitted, and improving the reliability of business transmission (such as emergency business or other business) for the remote terminal devices.

[0268] Please refer to Fig.16 , which shows a block diagram of a wireless communication device provided by another embodiment of the present application. The device has the function of implementing the above-mentioned method example executed by the second core network element side, and the function can be implemented by hardware, or by hardware executing corresponding software. The device can be implemented as a second core network element, or as a part of a second core network element. Fig.16 As shown, the device 1600 may include: a receiving module 1610 and a sending module 1620.

[0269] The receiving module 1610 is used to receive a first request message sent by a first core network network element, where the first request message is used to request identity information of a remote terminal device; wherein the remote terminal device accesses the network via a relay terminal device.

[0270] The sending module 1620 is used to send the identity information of the remote terminal device to the first core network network element, so that the first core network network element can authenticate the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0271] In some embodiments, the first request message includes an Internet Protocol IP address, a port number and third information of the remote terminal device, and the third information is used to indicate the acquisition of identity information of the remote terminal device.

[0272] In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI, PEI, GPSI, and MSISDN.

[0273] In some embodiments, the second core network element is a PCF.

[0274] The technical solution provided in the embodiment of the present application realizes SIP registration of remote terminal devices for relay scenarios, thereby ensuring that the business data of the remote terminal devices can be successfully transmitted, and improving the reliability of business transmission (such as emergency business or other business) for the remote terminal devices.

[0275] Please refer to Fig.17 , which shows a block diagram of a wireless communication device provided by another embodiment of the present application. The device has the function of implementing the method example executed by the third core network network element side, and the function can be implemented by hardware, or by hardware executing corresponding software. The device can be implemented as a third core network network element, or as a part of a third core network network element. Fig.17 As shown, the device 1700 may include: a receiving module 1710 and a sending module 1720 .

[0276] The receiving module 1710 is used to receive report information sent by the relay terminal device, where the report information includes device information of the remote terminal device; wherein the remote terminal device accesses the network through the relay terminal device.

[0277] The sending module 1720 is used to send a second request message to the fourth core network element, where the second request message is used to request to obtain the identity information of the remote terminal device, and the second request message includes the device information of the remote terminal device.

[0278] The receiving module 1710 is further used to receive a second response message from the fourth core network element, where the second response message includes the identity information of the remote terminal device.

[0279] The sending module 1720 is also used to send the identity information of the remote terminal device to the second core network network element, and the identity information of the remote terminal device is used to provide the first core network network element to authenticate the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0280] In some embodiments, the second request message includes fourth information, and the fourth information is used to indicate how to obtain the identity information of the remote terminal device.

[0281] In some embodiments, the device information includes at least one of the following: SUPI, SUCI.

[0282] In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI, PEI, GPSI, and MSISDN.

[0283] In some embodiments, the third core network element is an SMF.

[0284] The technical solution provided in the embodiment of the present application realizes SIP registration of remote terminal devices for relay scenarios, thereby ensuring that the business data of the remote terminal devices can be successfully transmitted, and improving the reliability of business transmission (such as emergency business or other business) for the remote terminal devices.

[0285] Please refer to Fig.18 , which shows a block diagram of a wireless communication device provided by another embodiment of the present application. The device has the function of implementing the method example executed by the fourth core network element side, and the function can be implemented by hardware, or by hardware executing corresponding software. The device can be implemented as a fourth core network element, or as a part of a core network element. Fig.18 As shown, the device 1800 may include: a receiving module 1810 and a sending module 1820.

[0286] The receiving module 1810 is used to receive a second request message sent by a third core network network element, wherein the second request message is used to request identity information of a remote terminal device, and the second request message includes device information of the remote terminal device; wherein the remote terminal device accesses the network via a relay terminal device.

[0287] The sending module 1820 is used to send a second response message to the third core network network element, and the second response message includes the identity information of the remote terminal device; wherein the identity information of the remote terminal device is used to provide the first core network network element to authenticate the remote terminal device to determine whether to accept the SIP registration request message initiated by the remote terminal device.

[0288] In some embodiments, the second request message includes fourth information, and the fourth information is used to indicate how to obtain the identity information of the remote terminal device.

[0289] In some embodiments, the device information includes at least one of the following: SUPI, SUCI.

[0290] In some embodiments, the identity information includes at least one of the following: IMPI, SUPI, SUCI, PEI, GPSI, and MSISDN.

[0291] In some embodiments, the fourth core network element is a UDM.

[0292] The technical solution provided in the embodiment of the present application realizes SIP registration of remote terminal devices for relay scenarios, thereby ensuring that the business data of the remote terminal devices can be successfully transmitted, and improving the reliability of business transmission (such as emergency business or other business) for the remote terminal devices.

[0293] Please refer to Fig.19 , which shows a schematic diagram of the structure of a terminal device provided by an embodiment of the present application. The terminal device 1900 may include: a processor 1901 , a transceiver 1902 , and a memory 1903 .

[0294] The processor 1901 includes one or more processing cores. The processor 1901 executes various functional applications and information processing by running software programs and modules.

[0295] The transceiver 1902 may include a receiver and a transmitter. For example, the receiver and the transmitter may be implemented as the same wireless communication component, and the wireless communication component may include a wireless communication chip and a radio frequency antenna.

[0296] The memory 1903 may be connected to the processor 1901 and the transceiver 1902 .

[0297] The memory 1903 may be used to store a computer program executed by the processor, and the processor 1901 is used to execute the computer program to implement each step executed by the remote terminal device or the relay terminal device in the above method embodiment.

[0298] In addition, memory 1903 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0299] For details not described in detail in this embodiment, please refer to the above embodiments, which will not be described in detail here.

[0300] Please refer to Fig. 20 , which shows a schematic diagram of the structure of a core network element provided by an embodiment of the present application. The core network element 2000 may include: a processor 2001, a transceiver 2002 and a memory 2003.

[0301] The processor 2001 includes one or more processing cores. The processor 2001 executes various functional applications and information processing by running software programs and modules.

[0302] The transceiver 2002 may include a receiver and a transmitter. For example, the transceiver 2002 may include a wired communication component, which may include a wired communication chip and a wired interface (such as an optical fiber interface). In some embodiments, the transceiver 2002 may also include a wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0303] The memory 2003 may be connected to the processor 2001 and the transceiver 2002 .

[0304] Memory 2003 may be used to store a computer program executed by the processor, and processor 2001 may be used to execute the computer program to implement the various steps executed by the first core network element, the second core network element, the third core network element, and the fourth core network element in the above method embodiment.

[0305] In addition, memory 2003 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and the volatile or non-volatile storage device includes but is not limited to: a magnetic disk or optical disk, an electrically erasable programmable read-only memory, an erasable programmable read-only memory, a static access memory, a read-only memory, a magnetic memory, a flash memory, and a programmable read-only memory.

[0306] For details not described in detail in this embodiment, please refer to the above embodiments, which will not be described in detail here.

[0307] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. The computer program is used to be executed by a processor of a first core network element to implement the wireless communication method on the first core network element side.

[0308] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. The computer program is used to be executed by a processor of a remote terminal device to implement the above-mentioned wireless communication method on the remote terminal device side.

[0309] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. The computer program is used to be executed by a processor of a relay terminal device to implement the wireless communication method on the relay terminal device side.

[0310] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. The computer program is used to be executed by a processor of a second core network element to implement the above-mentioned wireless communication method on the second core network element side.

[0311] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. The computer program is used to be executed by a processor of a third core network element to implement the above-mentioned wireless communication method on the third core network element side.

[0312] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. The computer program is used to be executed by a processor of a fourth core network element to implement the wireless communication method on the fourth core network element side.

[0313] In some embodiments, the computer readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives) or optical disks, etc. Among them, the random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0314] An embodiment of the present application also provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip runs on a first core network network element, it is used to implement the above-mentioned wireless communication method on the first core network network element side.

[0315] An embodiment of the present application further provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip runs on a remote terminal device, it is used to implement the above-mentioned wireless communication method on the remote terminal device side.

[0316] An embodiment of the present application further provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip runs on a relay terminal device, it is used to implement the wireless communication method on the relay terminal device side.

[0317] An embodiment of the present application also provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip runs on a second core network element, it is used to implement the above-mentioned wireless communication method on the second core network element side.

[0318] An embodiment of the present application also provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip runs on a third core network element, it is used to implement the above-mentioned wireless communication method on the third core network element side.

[0319] An embodiment of the present application also provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip runs on a fourth core network element, it is used to implement the above-mentioned wireless communication method on the fourth core network element side.

[0320] An embodiment of the present application also provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the first core network network element reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned wireless communication method on the first core network network element side.

[0321] An embodiment of the present application also provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the remote terminal device reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned wireless communication method on the remote terminal device side.

[0322] An embodiment of the present application also provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the relay terminal device reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned wireless communication method on the relay terminal device side.

[0323] An embodiment of the present application also provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the second core network network element reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned wireless communication method on the second core network network element side.

[0324] An embodiment of the present application also provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the third core network network element reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned wireless communication method on the third core network network element side.

[0325] An embodiment of the present application also provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the fourth core network network element reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned wireless communication method on the fourth core network network element side.

[0326] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0327] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0328] In some embodiments of the present application, "predefined" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a core network element), and the present application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0329] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, which is not limited in the present application.

[0330] The term "multiple" as used herein refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0331] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order to that shown in the figure. The embodiments of the present application are not limited to this.

[0332] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented with hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0333] The above description is only an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A wireless communication method, characterized in that: The method is performed by a remote terminal device, the remote terminal device accesses a network via a relay terminal device, and the method includes: Sending a Session Initiation Protocol (SIP) registration request message to the relay terminal device, wherein the SIP registration request message is sent by the relay terminal device to a first core network element in the network, and the SIP registration request message includes first information, and the first information is used to indicate that the remote terminal device accesses the network through a relay; Receive a SIP registration response message corresponding to the SIP registration request message from the first core network network element.

2. The method according to claim 1, characterized in that The relay mode is a layer 3 relay mode.

3. The method according to claim 1 or 2, characterized in that: The SIP registration response message is directly sent by the first core network element without executing an identity authentication process for the remote terminal device when it is determined according to the first information that the remote terminal device accesses the network via a relay.

4. The method according to claim 1 or 2, characterized in that: The SIP registration request message further includes second information, where the second information is used to indicate identity information of the remote terminal device, and the identity information includes at least one of the following: an IMS private user identity IMPI.

5. The method according to any one of claims 1 to 4, characterized in that: The first core network element is obtained by the remote terminal device through a Dynamic Host Configuration Protocol DHCP request; or, The first core network element is pre-configured.

6. A wireless communication method, characterized in that: The method is performed by a first core network element in the network, and the method includes: Receiving a Session Initiation Protocol (SIP) registration request message from a remote terminal device, the remote terminal device accessing the network through a relay terminal device, the SIP registration request message being sent by the remote terminal device to the first core network element through the relay terminal device, the SIP registration request message including first information, the first information being used to indicate that the remote terminal device accesses the network through a relay; Sending a SIP registration response message corresponding to the SIP registration request message to the remote terminal device.

7. The method according to claim 6, characterized in that The relay mode is a layer 3 relay mode.

8. The method according to claim 6 or 7, characterized in that: When it is determined according to the first information that the remote terminal device accesses the network via a relay, the first core network element does not execute an identity authentication process for the remote terminal device, and directly sends the SIP registration response message to the remote terminal device.

9. The method according to claim 6 or 7, characterized in that: The SIP registration request message also includes second information, where the second information is used to indicate identity information of the remote terminal device, and the identity information includes at least one of the following: an IMS private user identity IMPI.

10. The method according to any one of claims 6 to 9, characterized in that: The first core network element is obtained by the remote terminal device through a Dynamic Host Configuration Protocol DHCP request; or, The first core network element is pre-configured.

11. The method according to any one of claims 6 to 10, characterized in that: The first core network element is a proxy call session control function network element P-CSCF.

12. The method according to any one of claims 6 to 11, characterized in that The method further comprises: A first request message is sent to a policy control function network element PCF, where the first request message is used to request to obtain the identity information of the remote terminal device.

13. The method according to claim 12, characterized in that The method further comprises: Receive the identity information of the remote terminal device sent by the PCF, where the identity information includes: a user permanent identifier SUPI, a permanent equipment identifier PEI, or a general public user identifier GPSI.

14. A wireless communication device, characterized in that: The device comprises: A sending module, configured to send a Session Initiation Protocol (SIP) registration request message to a relay terminal device, wherein the SIP registration request message is sent by the relay terminal device to a first core network element in the network, and the SIP registration request message includes first information, wherein the first information is used to indicate that the remote terminal device accesses the network through a relay; The receiving module is used to receive a SIP registration response message corresponding to the SIP registration request message from the first core network network element.

15. A wireless communication device, characterized in that: The device comprises: A receiving module, configured to receive a Session Initiation Protocol (SIP) registration request message from a remote terminal device, wherein the remote terminal device accesses the network via a relay terminal device, wherein the SIP registration request message is sent by the remote terminal device to a first core network element via the relay terminal device, wherein the SIP registration request message includes first information, wherein the first information is used to indicate that the remote terminal device accesses the network via a relay; The sending module is used to send a SIP registration response message corresponding to the SIP registration request message to the remote terminal device.

16. A terminal device, characterized in that: The terminal device includes a processor, a transceiver and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the wireless communication method according to any one of claims 1 to 5.

17. A core network element, characterized in that: The core network element includes a processor, a transceiver and a memory, the memory stores a computer program, and the processor executes the computer program to implement the wireless communication method according to any one of claims 6 to 13.

Images