Communication method and communication device
By instructing the terminal device to the address through the core network, the terminal device can directly transmit signaling with the core network, which solves the problem of failure caused by too many AMF functions and improves the reliability of the communication system.
Patent Information
- Application Number
- PCT/CN2024/109921
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-05
- Publication Date
- 2026-02-12
AI Technical Summary
In traditional communication systems, the AMF serves as the signaling anchor point between terminal equipment and the core network, resulting in numerous functions, a high probability of failure, and impact on communication between terminal equipment and other core network elements.
The first network element in the core network indicates its address to the terminal device so that the terminal device can conduct signaling transmission with the core network based on the address. The AMF no longer serves as the anchor point for signaling transmission, reducing the functions it supports.
This reduces the impact of AMF failures on communication between terminal equipment and other core network elements, and reduces the probability of AMF failures.
Smart Images

Figure CN2024109921_12022026_PF_FP_ABST
Abstract
Description
Communication method and communication device TECHNICAL FIELD
[0001] The present application relates to the technical field of communication, and more particularly, to a communication method and a communication device. BACKGROUND
[0002] In a conventional communication system, the interaction between some core network elements supports a service interface, but the N1 interface between the terminal device and the AMF, the N2 interface between the access network element (AN) and the access and mobility management function (AMF) network element, and the N4 interface between the session management function (SMF) and the user plane function (UPF) still use a conventional reference point for interaction. However, the evolution of the service-based architecture is not complete. When the terminal device, the access network device, and the core network element perform signaling interaction, the AMF must be transferred. That is to say, in addition to mobility management, the AMF also serves as a NAS signaling anchor point for the terminal device and other core network elements (for example, the SMF, the authentication server function (AUSF), and the like), which means that the AMF must also participate in session management and security management support (for example, identity verification, encryption / decryption), and therefore, compared with other core network functions, the AMF has more supported functions, resulting in a higher probability of AMF failure. Once the AMF fails, it will seriously affect the communication between the terminal device and other core network elements.
[0003] SUMMARY
[0004] The present application provides a communication method and a communication device. The various aspects involved in the present application are introduced below.
[0005] In a first aspect, a communication method is provided, including: a terminal device receiving a first message sent by a first network element in a core network, the first message containing an address of the terminal device, and the address of the terminal device being used for transmission of signaling between the terminal device and the core network.
[0006] In a second aspect, a communication method is provided, including: a first network element in a core network sending a first message to a terminal device, the first message containing an address of the terminal device, and the address of the terminal device being used for transmission of signaling between the terminal device and the core network.
[0007] In a third aspect, a communication method is provided, including: receiving, by a second network element in a core network, a second message, the second message including an identifier of a terminal device and an address of the terminal device, the address of the terminal device being used for signaling transmission between the terminal device and the core network.
[0008] In a fourth aspect, a communication method is provided, including: sending, by a terminal device, a fifth message to a target network element, the fifth message being used to indicate that the terminal device supports address-based signaling transmission.
[0009] In a fifth aspect, a communication method is provided, including: receiving, by a target network element, a fifth message sent by a terminal device, the fifth message being used to indicate that the terminal device supports address-based signaling transmission.
[0010] In a sixth aspect, a communication method is provided, including: receiving, by an access network device, a seventh message sent by a terminal device, the seventh message including one or more of: first non-access stratum (NAS) signaling, the first NAS signaling being NAS signaling sent by the terminal device to a fourth network element in a core network; an address of the terminal device; an address of the fourth network element.
[0011] In a seventh aspect, a communication method is provided, including: sending, by a terminal device, a seventh message to an access network device, the seventh message including one or more of: first NAS signaling, the first NAS signaling being NAS signaling sent by the terminal device to a fourth network element in a core network; an address of the terminal device; an address of the fourth network element.
[0012] In an eighth aspect, a communication method is provided, including: receiving, by a fourth network element in a core network, a first data packet sent by an access network device, the first data packet being an address-based transmission data packet, and the first data packet including first NAS signaling sent by a terminal device to the fourth network element.
[0013] In a ninth aspect, a communication method is provided, including: receiving, by a third network element of a core network, a third data packet sent by an access network device, the third data packet being an address-based transmission data packet, and the third data packet including first information, the first information being used to request an address of a fourth network element in the core network from the third network element.
[0014] In a tenth aspect, a communication method is provided, including: receiving, by an access network device, a fifth data packet sent by a fourth network element in a core network, the fifth data packet being an address-based transmission data packet, and the fifth data packet including third NAS signaling, the third NAS signaling being NAS signaling sent by the fourth network element to a terminal device.
[0015] In a eleventh aspect, a communication method is provided, comprising: sending, by a fourth network element in a core network, a fifth data packet to an access network device, the fifth data packet being a data packet for address-based signaling transmission, and the fifth data packet containing third NAS signaling, the third NAS signaling being NAS signaling sent by the fourth network element to a terminal device.
[0016] In a twelfth aspect, a communication method is provided, comprising: receiving, by a second network element in a core network, a twelfth message sent by a fourth network element, the twelfth message being used for requesting an address of a terminal device and / or an address of an access network device serving the terminal device; wherein the address of the terminal device is used for signaling transmission between the terminal device and the core network.
[0017] In a thirteenth aspect, a communication method is provided, comprising: receiving, by a terminal device, an eleventh message sent by an access network device, the eleventh message containing one or more of the following: third NAS signaling, the third NAS signaling being NAS signaling sent by a fourth network element in a core network to the terminal device; an address of the fourth network element; and an address of the terminal device.
[0018] In a fourteenth aspect, a terminal device is provided, comprising: a receiving unit configured to receive a first message sent by a first network element in a core network, the first message containing an address of the terminal device, the address of the terminal device being used for signaling transmission between the terminal device and the core network.
[0019] In a fifteenth aspect, a communication device is provided, the communication device being a first network element in a core network, comprising: a sending unit configured to send a first message to a terminal device, the first message containing an address of the terminal device, the address of the terminal device being used for signaling transmission between the terminal device and the core network.
[0020] In a sixteenth aspect, a communication device is provided, the communication device being a second network element in a core network, comprising: a receiving unit configured to receive a second message, the second message including an identifier of a terminal device and an address of the terminal device, the address of the terminal device being used for signaling transmission between the terminal device and the core network.
[0021] In a seventeenth aspect, a terminal device is provided, comprising: a sending unit configured to send a fifth message to a target network element, the fifth message being used to indicate that the terminal device supports address-based signaling transmission.
[0022] In an eighteenth aspect, a communication device is provided, wherein the communication device is a target network element, and the communication device comprises a receiving unit configured to receive a fifth message sent by a terminal device, wherein the fifth message is used to indicate that the terminal device supports signaling-based transmission.
[0023] In a nineteenth aspect, a communication device is provided, wherein the communication device is an access network device, and the communication device comprises a receiving unit configured to receive a seventh message sent by a terminal device, wherein the seventh message comprises one or more of the following: first NAS signaling, wherein the first NAS signaling is NAS signaling sent by the terminal device to a fourth network element in a core network; an address of the terminal device; and an address of the fourth network element.
[0024] In a twentieth aspect, a terminal device is provided, and the terminal device comprises a sending unit configured to send a seventh message to an access network device, wherein the seventh message comprises one or more of the following: first NAS signaling, wherein the first NAS signaling is NAS signaling sent by the terminal device to a fourth network element in a core network; an address of the terminal device; and an address of the fourth network element.
[0025] In a twenty-first aspect, a communication device is provided, wherein the communication device is a fourth network element in a core network, and the communication device comprises a receiving unit configured to receive a first data packet sent by an access network device, wherein the first data packet is an address-based transmission data packet, and the first data packet comprises first NAS signaling sent by a terminal device to the fourth network element.
[0026] In a twenty-second aspect, a communication device is provided, wherein the communication device is a third network element in a core network, and the communication device comprises a receiving unit configured to receive a third data packet sent by an access network device, wherein the third data packet is an address-based transmission data packet, and the third data packet comprises first information, wherein the first information is used to request an address of a fourth network element in the core network from the third network element.
[0027] In a twenty-third aspect, a communication device is provided, wherein the communication device is an access network device, and the communication device comprises a receiving unit configured to receive a fifth data packet sent by a fourth network element in a core network, wherein the fifth data packet is an address-based transmission data packet, and the fifth data packet comprises third NAS signaling, wherein the third NAS signaling is NAS signaling sent by the fourth network element to a terminal device.
[0028] In a twenty-fourth aspect, a communication device is provided. The communication device is a fourth network element in a core network. The communication device comprises a sending unit configured to send a fifth data packet to an access network device, the fifth data packet being a data packet based on address transmission, and the fifth data packet comprising third NAS signaling, the third NAS signaling being NAS signaling sent by the fourth network element to a terminal device.
[0029] In a twenty-fifth aspect, a communication device is provided. The communication device is a second network element in a core network. The communication device comprises a receiving unit configured to receive a twelfth message sent by a fourth network element, the twelfth message being used to request an address of a terminal device and / or an address of an access network device serving the terminal device, and wherein the address of the terminal device is used for signaling transmission between the terminal device and the core network.
[0030] In a twenty-sixth aspect, a terminal device is provided. The terminal device comprises a receiving unit configured to receive an eleventh message sent by an access network device, the eleventh message comprising one or more of the following: third NAS signaling, the third NAS signaling being NAS signaling sent by a fourth network element in a core network to the terminal device; an address of the fourth network element; and an address of the terminal device.
[0031] In a twenty-seventh aspect, a terminal device is provided. The terminal device comprises a processor, a memory, and a communication interface. The memory is configured to store one or more computer programs. The processor is configured to invoke the computer programs in the memory, so that the terminal device performs some or all of the steps in the methods of the various aspects described above.
[0032] In a twenty-eighth aspect, a network device is provided. The network device comprises a processor, a memory, and a transceiver. The memory is configured to store one or more computer programs. The processor is configured to invoke the computer programs in the memory, so that the network device performs some or all of the steps in the methods of the various aspects described above.
[0033] In a twenty-ninth aspect, an embodiment of the present application provides a communication system. The system comprises the terminal device and / or the network device described above. In another possible design, the system can further comprise other devices interacting with the terminal device or the network device in the solutions provided by the embodiments of the present application.
[0034] In a thirtieth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. The computer program causes a communication device (e.g., a terminal device or a network device) to perform some or all of the steps in the methods of the various aspects described above.
[0035] In a thirty-first aspect, an embodiment of the present application provides a computer program product. The computer program product includes a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to cause an apparatus (for example, a terminal device or a network device) to perform some or all of the steps of any of the methods in the various aspects described above. In some implementations, the computer program product can be a software installation package.
[0036] In a thirty-second aspect, an embodiment of the present application provides a chip. The chip includes a memory and a processor. The processor can invoke and run a computer program from the memory to implement some or all of the steps described in the methods of the various aspects described above.
[0037] In the embodiments of the present application, the first network element in the core network can indicate the address of the terminal device to the terminal device, so that the terminal device transmits signaling with the core network based on the address of the terminal device. That is to say, in this scheme, the AMF is no longer an anchor point for the terminal device to transmit signaling with the core network. Compared with the traditional scheme in which the AMF is an anchor point for the terminal device to transmit signaling with the core network, the influence of AMF failure on the communication between the terminal device and other core network elements is reduced. BRIEF DESCRIPTION OF DRAWINGS
[0038] FIG. 1 is a schematic diagram of a communication system architecture to which embodiments of the present application are applicable.
[0039] FIG. 2 is a schematic flowchart of a communication method in an embodiment of the present application.
[0040] FIG. 3 is a schematic flowchart of a scheme for allocating an address of a terminal device to the terminal device in an embodiment of the present application.
[0041] FIG. 4 is a schematic flowchart of a communication method in an embodiment of the present application.
[0042] FIG. 5 is a schematic flowchart of a scheme for capability negotiation between a terminal device, an access network device, and a core network element in an embodiment of the present application.
[0043] FIG. 6 is a schematic flowchart of a communication method in an embodiment of the present application.
[0044] FIG. 7 is a schematic diagram of a first data packet in an embodiment of the present application.
[0045] FIG. 8 is a schematic diagram of a second data packet in an embodiment of the present application.
[0046] FIG. 9 is a schematic diagram of a third data packet in an embodiment of the present application.
[0047] FIG. 10 is a schematic diagram of a fourth data packet in an embodiment of the present application.
[0048] Figure 11 is a schematic flow chart of a process of communication between a terminal device and a core network in an MO scenario according to an embodiment of the application.
[0049] Figure 12 is a schematic flow chart of a communication method according to an embodiment of the application.
[0050] Figure 13 is a schematic diagram of a fifth data packet according to an embodiment of the application.
[0051] Figure 14A is a schematic flow chart of a process of communication between a terminal device and a core network in an MT scenario according to an embodiment of the application.
[0052] Figure 14B is a schematic flow chart of a process of communication between a terminal device and a core network in an MT scenario according to an embodiment of the application.
[0053] Figures 15 and 16 are schematic diagrams of protocol stacks according to embodiments of the application.
[0054] Figure 17 is a schematic diagram of a terminal device according to an embodiment of the application.
[0055] Figure 18 is a schematic diagram of a communication device according to an embodiment of the application.
[0056] Figure 19 is a schematic diagram of a communication device according to an embodiment of the application.
[0057] Figure 20 is a schematic diagram of a terminal device according to an embodiment of the application.
[0058] Figure 21 is a schematic diagram of a communication device according to an embodiment of the application.
[0059] Figure 22 is a schematic diagram of a communication device according to an embodiment of the application.
[0060] Figure 23 is a schematic diagram of a terminal device according to an embodiment of the application.
[0061] Figure 24 is a schematic diagram of a communication device according to an embodiment of the application.
[0062] Figure 25 is a schematic diagram of a communication device according to an embodiment of the application.
[0063] Figure 26 is a schematic diagram of a communication device according to an embodiment of the application.
[0064] Figure 27 is a schematic diagram of a communication device according to an embodiment of the application.
[0065] Figure 28 is a schematic diagram of a communication device according to an embodiment of the application.
[0066] Figure 29 is a schematic diagram of a terminal device according to an embodiment of the application.
[0067] Figure 30 is a schematic block diagram of a communication apparatus according to an embodiment of the application. DETAILED DESCRIPTION
[0068] The technical solutions in the present application will be described below with reference to the drawings.
[0069] FIG. 1 is a schematic diagram of a communication system architecture to which embodiments of the present application are applicable. The network architecture can include terminal devices, access network (AN) network elements, and core network network elements.
[0070] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as a 5th generation (5G) system or new radio (NR), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), and the like. The technical solutions provided in the present application can also be applied to future communication systems, such as a 6th generation mobile communication system, a satellite communication system, and the like.
[0071] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), an MT, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless core network network element, a user agent or a user apparatus. The terminal device in the embodiments of the present application can refer to a device that provides voice and / or data connectivity for a user, and can be used to connect people, things and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, which provides sidelink signals between terminal devices in vehicle-to-everything (V2X) or device to device (D2D), etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and the smart home device communicate with each other without relaying the communication signals through the base station.
[0072] The access network element can be an access network device. The access network element can be an access device through which a terminal accesses the network architecture by wireless means, and is mainly responsible for wireless resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side. The access network element can also be referred to as a radio access network (RAN) device, for example, the access network element can be a base station. The base station can broadly cover various names in the following or replace the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station can also refer to a communication module, modem, or chip used in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs the function of a base station in D2D, V2X, machine-to-machine (M2M) communication, a network side device in a 6G network, a device that performs the function of a base station in a future communication system, etc. The base station can support networks of the same or different access technologies. Embodiments of the present application do not limit the specific technology and specific device form adopted by the access network element.
[0073] The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, the helicopter or the drone can be configured to act as a device that communicates with another base station.
[0074] In some deployments, the access network element in the embodiments of the present application can refer to a CU or a DU, or the access network element includes a CU and a DU. The gNB can also include an AAU.
[0075] The type of the network element in the core network (also referred to as "network function (NF, or "core network element") can include a UPF network element, an AMF network element, an SMF network element, a PCF network element, an application function (AF), a data network (DN), a network slice selection function (NSSF), an AUSF, a unified data management function (UDM), a network exposure function (NEF), a network repository function (NRF), and a network slice-specific authentication and authorization function (NSSAAF). Among them, the UPF network element is mainly responsible for the transmission of user data, and other network elements can be referred to as control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control, etc. to ensure reliable and stable transmission of user data.
[0076] The UPF network element can be used to forward and receive data of the terminal. For example, the UPF network element can receive service data from a data network and transmit it to the terminal through the access network element; the UPF network element can also receive user data from the terminal through the access network element and forward it to the data network. Among them, the transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element can include a user plane connection between the UPF network element and the access network element, and a channel established between the access network element and the terminal. Among them, the user plane connection is a QoS flow that can be established between the UPF network element and the access network element to transmit data.
[0077] The AMF network element can be used to manage the access of the terminal to the core network, such as location update of the terminal, registration network, access control, mobility management of the terminal, attachment and detachment of the terminal, etc. The AMF network element can also provide storage resources for the control plane of the session for the terminal in the case of providing services for the session, to store the session identifier, the SMF network element identifier associated with the session identifier, etc.
[0078] The SMF network element can be used to select a user plane network element for a terminal, redirect a user plane network element for a terminal, assign an internet protocol (IP) address for a terminal, establish a bearer (also referred to as a session) between the terminal and a UPF network element, modify and release the session, and control QoS.
[0079] The PCF network element is used to provide policies such as QoS policies and slice selection policies to the AMF network element and the SMF network element.
[0080] The AF network element is used to interact with 3GPP core network elements to support application-affected data routing, access network exposure functions, and interact with the PCF network element for policy control.
[0081] The DN can provide data services for users, such as IP multi-media service (IMS) networks and the Internet. There can be various application servers (ASs) in the DN to provide different application services, such as operator services, Internet access, or third-party services. The AS can implement the functions of the AF.
[0082] The NSSF is used for network slice selection and supports the following functions: selecting a set of network slice instances to serve a terminal device; determining allowed network slice selection assistance information (NSSAI) and, if necessary, determining the mapping to single-network slice selection assistance information (S-NSSAI) of a subscription; determining configured NSSAI and, if necessary, determining the mapping to S-NSSAI of a subscription; and determining a set of AMFs that can be queried for a terminal device or determining a list of candidate AMFs based on configuration.
[0083] The AUSF is used to receive a request from the AMF for terminal authentication, request a key from the UDM, and forward the delivered key to the AMF for authentication processing.
[0084] The UDM includes functions such as generation and storage of user subscription data and management of authentication data, and supports interaction with external third-party servers.
[0085] The NEF is used for capability exposure, that is, based on the NEF, the capabilities of the network can be output to external networks. External non-trusted applications can access internal data of the core network through the NEF to ensure the security of the network. The NEF can provide functions such as external application QoS capability exposure, event subscription, and AF request distribution.
[0086] The NRF is used for core network element registration, management, and state detection, thereby enabling automatic management of core network elements. When a core network element is started, it must be registered with the NRF to provide services. The registration information may, for example, include the type, address, service list, and the like of the core network element.
[0087] In addition, some networks (for example, 5G networks) also add a network data analysis function (network data analytics function, NWDAF) in the core network. Based on the NWDAF, data can be collected from various network elements, network management systems, and the like in the core network, and big data statistics, analysis, or intelligent data analysis can be performed, thereby obtaining network-side analysis or prediction data, and further assisting various network elements in more effectively controlling terminal device access based on the data analysis results.
[0088] In some communication systems (for example, 5G systems), core network elements can also be referred to as network functions (network function, NF).
[0089] The network elements in FIG. 1 can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). It should be noted that in the network architecture shown in the above figure, only the network elements included in the entire network architecture are exemplarily illustrated. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.
[0090] Those skilled in the art can understand that the network architecture shown in FIG. 1 does not constitute a limitation on the network architecture, and in actual implementation, the network architecture can include more or fewer network elements than those shown, or some network elements can be combined, and the like. It should be understood that the AN or RAN is represented in the form of (R)AN in FIG. 1.
[0091] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; and can also be deployed on aircraft, balloons, and satellites in the air. The scenarios in which the network devices and terminal devices are located are not limited in the embodiments of the present application.
[0092] By way of example, and without limitation, in embodiments of the present application, a network device can have a mobile characteristic, for example, the network device can be a mobile device. In some embodiments of the present application, the network device can be a satellite, a balloon station. For example, the satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) satellite, etc. In some embodiments of the present application, the network device can also be a base station arranged at a location on land, water, etc.
[0093] In embodiments of the present application, a network device can serve a cell, and a terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell. The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cell can include a metro cell, a micro cell, a pico cell, a femto cell, etc., and these small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
[0094] It should be understood that the "indication" mentioned in the embodiments of the present application can be direct indication, or indirect indication, or can be an indication of an associated relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can obtain through A; or A indirectly indicates B, for example, A indicates C, and B can obtain through C; or A and B have an associated relationship.
[0095] In the description of embodiments of the present application, the term "corresponding" can mean a direct or indirect corresponding relationship between the two, or an associated relationship between the two, or an indication and being indicated, configuration and being configured, etc.
[0096] The "configuration" in the embodiments of the present application can include at least one of system message, radio resource control (RRC) signaling and media access control control element (MAC CE).
[0097] In some embodiments of the present application, "predefined" or "preset" can be implemented by pre-storing corresponding codes, tables or other means for indicating relevant information in devices (for example, including terminal devices and network devices), and the specific implementation manner is not limited in the present application. For example, predefined can refer to defined in a protocol.
[0098] In some embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, which can include the LTE protocol, the NR protocol and the related protocol applied to the future communication system, and the present application is not limited to this.
[0099] Based on the communication system shown in FIG. 1, it can be seen that the interaction between some core network elements supports the service interface, but the N1 interface between the terminal device and the AMF, the N2 interface between the AN and the AMF, and the N4 interface between the SMF and the UPF still use the traditional reference point for interaction. However, the evolution of the service-based architecture is not complete. When the terminal device, the access network device and the core network element perform signaling interaction, the AMF must be transferred. That is to say, in addition to mobility management, the AMF also acts as a NAS signaling anchor point for the terminal device and other core network elements (for example, the session management function, the AUSF, etc.), which means that the AMF must also participate in the session management and security management support (for example, identity verification, encryption / decryption), so that the AMF has more functions compared with other core network functions, which leads to a higher probability of AMF failure. Once the AMF fails, it will seriously affect the communication between the terminal device and other core network elements.
[0100] Therefore, in view of the above problems, the embodiments of the present application provide a communication method, in which a first network element in the core network can indicate the address of the terminal device to the terminal device, so that the terminal device transmits signaling with the core network based on the address of the terminal device. That is to say, in this scheme, the AMF is no longer an anchor point for the terminal device and the core network to transmit signaling, which helps to reduce the impact of AMF failure on the communication between the terminal device and other core network elements compared with the traditional scheme in which the AMF is an anchor point for the terminal device and the core network to transmit signaling.
[0101] On the other hand, the AMF is no longer an anchor point for the terminal device and the core network to transmit signaling, and accordingly, the functions supported by the AMF can be reduced accordingly, which helps to reduce the probability of AMF failure.
[0102] In some implementations, the address of the terminal device can include an IP address of the terminal device and / or a MAC address of the terminal device. Taking an example in which the address of the terminal device includes an internet protocol (IP) address of the terminal device, the IP address of the terminal device can be a globally unique Internet Protocol Version 6 (IPv6) address of the terminal device.
[0103] In some implementations, the address of the terminal device and the address of the access network device belong to different address sets. For example, the prefix of the IPv6 address of the terminal device is different from the prefix of the IPv6 address of the access network device, which helps other network elements to distinguish whether the source of the NAS message is the terminal device or the access network device according to the prefix of the IPv6 address.
[0104] In the embodiments of the present application, the first network element is not limited. In some implementations, the first network element can be a network element that allocates an address for a terminal device. For example, the first network element can be a dynamic host configuration protocol (DHCP) proxy network element. In the embodiments of the present application, the DHCP proxy network element is not limited. For example, the DHCP proxy network element can include one of the following: an authentication service function, a unified data management function, and a mobility management network element.
[0105] It should be understood that the network element involved in the embodiments of the present application can be the 5G core network element introduced above, or a network element having the same or similar function in a future 6G system. Hereinafter, the 5G core network element is taken as an example for introduction.
[0106] For ease of understanding, the communication method in the embodiments of the present application is introduced below in combination with FIG. 2. The communication method shown in FIG. 2 includes step S210.
[0107] In step S210, the first network element in the core network sends a first message to the terminal device, and the first message contains an address of the terminal device.
[0108] In some implementations, the first message contains the address of the terminal device, which can be understood as that the first message is used to configure the address of the terminal device for the terminal device. Therefore, the first message can also be referred to as configuration information or address configuration information.
[0109] In some implementations, the process in which the first network element configures the address of the terminal device for the terminal device can be implemented through a terminal device configuration update process. At this time, the first message can be used to update the configuration for the terminal device.
[0110] In some embodiments, the address of the terminal device is used for transmission of signaling between the terminal device and the core network, for example, the address of the terminal device is used for transmission of signaling between the terminal device and a network element in the core network, wherein the network element in the core network can be a network element serving the terminal device. The embodiments of the present application do not limit the network element in the core network, for example, the network element can be the SMF, AMF, NRF introduced in the foregoing, of course, in the embodiments of the present application, the network element can also be a newly introduced network element in the 6G network.
[0111] In some embodiments, the signaling can be control plane signaling, that is, the address of the terminal device is allocated by the first network element to the terminal device in the control plane, so that the terminal device can perform transmission of control plane signaling based on the address. Of course, in the embodiments of the present application, the signaling can be user plane signaling, that is, the signaling can be transmitted through the control plane or the data plane.
[0112] For example, the signaling is transmitted on the uu interface (for example, between the terminal device and the access network device) using the signaling radio bearer (SRB) or the data radio bearer (DRB), and subsequently, the transmission between the access network device and the network element in the core network can be directly through the service-based interface (SBI) or through the data plane connection (for example, the PDU session on the N3 interface) by the UPF.
[0113] In some embodiments, the first message further includes one or more of the following: an identifier of the terminal device; an address and / or a fully qualified domain name (FQDN) of a third network element in the core network; an address and / or a FQDN of one or more fourth network elements in the core network; a security parameter; slice information. In the embodiments of the present application, the combination of various information in the first message is not limited.
[0114] Taking the first message including the identifier of the terminal device as an example, in some embodiments, the terminal device identifier can include one or more of the following: SUPI, SUCI, GPSI.
[0115] Taking the first message including the address and / or FQDN of the third network element in the core network as an example, that is, the first message includes the address of the third network element in the core network, or the first message includes the FQDN of the third network element in the core network, or the first message includes the address and the FQDN of the third network element in the core network.
[0116] In some implementations, the third network element is configured to discover other network elements in the core network, for example, the third network element can be an NRF. Of course, in the embodiments of the present application, the third network element can be other network elements with similar functions. In the embodiments of the present application, by carrying the address and / or FQDN of the third network element in the first message, it is helpful for the terminal device to discover other network elements through the third network element in subsequent communication, and to directly communicate with other network elements based on the address of the terminal device.
[0117] In some implementations, the address of the third network element can include an IP address of the third network element and / or a MAC address of the third network element.
[0118] In some implementations, if the first message contains the FQDN of the third network element (for example, the first message does not contain the address of the third network element, but only contains the FQDN of the third network element), at this time, the terminal device can query the address in the third network element from the server (for example, the DHCP server) based on the FQDN of the third network element.
[0119] In the embodiments of the present application, if the first message can include the address of the third network element, the terminal device can directly communicate with the third network element based on the address of the third network element, so as to reduce the latency of the terminal device and the third network element. On the other hand, if the first network element does not store the address of the third network element, the first network element can send the FQDN of the third network element to the terminal device, so that the terminal device can obtain the address of the third network element, and communicate with the third network element based on the address of the terminal device and the address of the third network element, which is helpful to expand the applicable scenarios of the present application.
[0120] For example, the first message includes the address and / or FQDN of one or more fourth network elements in the core network, that is, the first message includes the address of the fourth network element in the core network, or the first message includes the FQDN of the fourth network element in the core network, or the first message includes the address and FQDN of the fourth network element in the core network.
[0121] In some implementations, the fourth network element is a network element in the core network for serving the terminal device, for example, the fourth network element can be an AMF, an SMF, or an AUSF, etc.
[0122] In some implementations, the first message can also indicate the type of the fourth network element, wherein the type of the fourth network element is used to indicate the function of the fourth network element. Therefore, the first message for indicating the type of the fourth network element can be replaced by the first message for indicating the function of the fourth network element. For example, the fourth network element is a DHCP proxy (such as AUSF), and the type of the fourth network element is AUSF.
[0123] For example, the security parameter included in the first message is used for the terminal device to establish a security context with a network element in the core network. For example, the security parameter is used for the terminal device to establish a security context with the NRF, which helps the terminal device to communicate with the NRF through the security context between the terminal device and the NRF, so as to discover other network elements.
[0124] In some scenarios, the security parameter used for the terminal device to establish a security context with a network element in the core network can be understood as the security parameter used for the terminal device to establish a security association with the NRF. The security association is also referred to as a security relationship, a security association, a security group, a security parameter combination, etc. Generally, in order to provide a secure communication environment, a shared network security attribute can be created between the terminal device and the network element in the core network. In a security relationship, network data parameters can be exchanged before network connection, including encryption mode and encryption algorithm, security encryption key, etc. These parameters can be an example of the security parameter described above. Accordingly, the network security relationship and the key management protocol can provide a basic framework for the security relationship, and the Internet Key Exchange provides a key exchange mechanism.
[0125] For example, the slice information of the terminal device included in the first message helps to inform the terminal device of the slice used for communication with the network element in the core network.
[0126] In some implementations, different slices can correspond to different addresses of the terminal device, which helps to improve the flexibility of address setting of the terminal device. Therefore, the slice information in the first message can be used to indicate the slice using the address of the terminal device.
[0127] In the embodiments of the present application, the sending time of the first message is not limited. In some implementations, before step S210, the terminal device registers to the core network. That is to say, if the terminal device registers to the core network, the first network element can allocate the address of the terminal device to the terminal device through the first message, so that the terminal device performs signaling interaction with the network element in the core network based on the address of the terminal device. In another implementation, before step S210, the terminal device performs network slice identity authentication and / or authentication successfully. That is to say, if the terminal device performs network slice identity authentication and / or authentication successfully, the first network element can allocate the address of the terminal device associated with the network slice to the terminal device through the first message, so that the terminal device performs signaling interaction with the network element in the core network through the network slice based on the address of the terminal device.
[0128] In some scenarios, the first network element can not store the address of the terminal device, and in this case, the first network element can request the server to allocate the address of the terminal device for the terminal device, where the server can be a DHCP server. That is, before step S210, the above method further includes: the first network element sends a third message to the server, where the third message is used to request the server to allocate the address of the terminal device for the terminal device; and the first network element receives the address of the terminal device sent by the server.
[0129] In some implementations, the third message is used to request the server to allocate the address of the terminal device, and therefore, the third message is also referred to as an "address request".
[0130] In some implementations, the third message contains the identifier of the terminal device and / or the slice information of the terminal device. Taking the case that the third message contains the identifier of the terminal device as an example, the identifier of the terminal device can include one or more of the following: a subscription permanent identifier (SUPI), a subscription concealed identifier (SUCI), and a generic public subscription identifier (GPSI). Taking the case that the third message contains the slice information of the terminal device as an example, the slice information can include S-NSSAI, so that the server allocates the address of the terminal device associated with the slice information for the terminal device, where the address of the terminal device associated with the slice information can be understood as the address of the terminal device used on the network slice indicated by the slice information. Of course, in the embodiments of the present application, the third message can contain the identifier of the terminal device and the slice information of the terminal device.
[0131] In some implementations, the third message can be sent after the terminal device successfully registers to the core network. Of course, in the embodiments of the present application, the third message can also be sent at other times.
[0132] The above introduces the scheme for allocating the address of the terminal device for the terminal device in the embodiments of the present application, and the following introduces the schemes for obtaining the address of the terminal device by other network elements in the embodiments of the present application in combination with implementation 1 to implementation 4. It should be understood that in the embodiments of the present application, implementation 1 to implementation 4 can be used independently of each other, or implementation 1 to implementation 4 can be used in combination with each other. For example, implementation 2, implementation 3, and implementation 4 can be used in combination with each other. For another example, implementation 2 and implementation 3 can be used in combination with each other. For another example, implementation 1 and implementation 2 can be used in combination with each other. Of course, in the embodiments of the present application, implementation 1, implementation 2, implementation 3, and implementation 4 can be used in combination with each other.
[0133] In implementation 1, the first network element can send the address of the terminal device to a second network element in the core network, so that the second network element stores the address of the terminal device, and other network elements can query the address of the terminal device from the second network element. Generally, in order for the second network element to determine the terminal device corresponding to the address of the terminal device, the first network element can also send the identity of the terminal device to the second network element. That is, the above method further includes: the first network element sends a second message to the second network element in the core network, and the second message includes the identity of the terminal device and the address of the terminal device. For example, the second message can include the mapping relationship between the identity of the terminal device and the address of the terminal device.
[0134] In some implementations, the second network element includes a UDM and / or a UDR. Of course, in the embodiments of the present application, the second network element can also be a network element with the same or similar function in a future communication system.
[0135] It should be noted that the identity of the terminal device included in the second message can be a terminal device identity for NAS layer interaction, so that the network element in the core network can identify based on the terminal device identity.
[0136] In implementation 2, if the terminal device obtains the address of the terminal device, the terminal device can inform the access network device of the address of the terminal device, so that the access network device can identify the terminal device based on the address of the terminal device. That is, the above method further includes: the terminal device sends a fourth message to the access network device, and the fourth message includes the address of the terminal device.
[0137] In some implementations, the fourth message can also carry the identity of the terminal device, so that the access network device can determine the terminal device corresponding to the address of the terminal device based on the identity of the terminal device. For example, the fourth message can include the mapping relationship between the identity of the terminal device and the address of the terminal device.
[0138] In some implementations, the identity of the terminal device can be an identity used by the access network device to page the terminal device, for example, the identity of the terminal device can include a globally unique temporary identity (GUTI) and / or a 5G-short term mobile subscriber identity (5G-S-TMSI).
[0139] In the embodiments of the present application, the fourth message is not limited. In some implementations, the fourth message is an AS message. In this way, the access network device can obtain the address of the terminal device from the AS message, which helps to simplify the complexity of the access network device obtaining the address of the terminal device. In other implementations, the fourth message is a NAS message, for example, the fourth message can be encapsulated in a NAS container. At this time, the fourth message is transparent to the access network device, and the access network device can obtain the address of the terminal device from the core network receiving the fourth message, that is, the address of the terminal device is invisible in the air interface transmission process, which helps to improve the security of transmitting the fourth message.
[0140] In implementation 3, if the access network device obtains the fourth message, the access network device can send the fourth message to the UDM, so that the UDM stores the address of the terminal device for other network elements in the core network to query. As described above, the fourth message can include the identifier of the terminal device and the address of the terminal device, and at this time the UDM stores the address of the terminal device and the identifier of the terminal device, for example, the mapping relationship between the address of the terminal device and the identifier of the terminal device.
[0141] In the embodiments of the present application, the transmission mode of the fourth message is not limited. In some implementations, the access network device can send the fourth message to the UDM through the NRF. In other implementations, the access network device can also directly send the fourth message to the UDM.
[0142] In implementation 4, if the access network device obtains the fourth message, the access network device can send the fourth message to the NRF, so that the NRF stores the address of the terminal device. As described above, the fourth message can include the identifier of the terminal device and the address of the terminal device, and at this time the UDM stores the address of the terminal device and the identifier of the terminal device. For example, the UDM stores the mapping relationship between the address of the terminal device and the identifier of the terminal device.
[0143] In order to facilitate understanding, the following takes the DHCP proxy network element as an example, and introduces the scheme for allocating the address of the terminal device to the terminal device in the embodiments of the present application in combination with FIG. 3. The method shown in FIG. 3 includes steps S310 to S365. It should be understood that the method shown in FIG. 3 mainly introduces the method flow, and the related information can be referred to the above.
[0144] In step S310, the terminal device successfully registers to the core network.
[0145] In step S315, the DHCP proxy network element sends an address request to the DHCP server, and the address request is used to request to allocate an address to the terminal device (as an example of the third message).
[0146] In some implementations, the address request carries a terminal device identifier and / or an S-NSSAI.
[0147] In step S320, the DHCP server finds an address (e.g., an IPv6 address) that is not assigned to other terminal devices, and sends the address to the DHCP proxy network element as a response message.
[0148] In some implementations, the address assigned to the terminal device and the address assigned to the access network device are not in the same address set. For example, the prefix of the IPv6 address assigned to the terminal device is different from the prefix of the IPv6 address assigned to the access network device, which helps other network elements to determine whether the source of the NAS message is the terminal device or the access network device according to the prefix of the IPv6 address.
[0149] In step S325, the DHCP proxy network element stores the identifier of the terminal device and the address of the terminal device, wherein the identifier of the terminal device can include the terminal device identifier of NAS layer interaction, such as SUPI, SUCI, and GPSI.
[0150] In step S330, the DHCP proxy network element sends a second message to the UDM, and the second message includes the identifier of the terminal device and the address of the terminal device. For example, the second message can include the mapping relationship between the identifier of the terminal device and the address of the terminal device.
[0151] In step S335, the DHCP proxy network element sends a first message to the terminal device, and the first message contains the address of the terminal device.
[0152] In some implementations, the first message includes the address of the terminal device; the identifier of the terminal device; the address and / or FQDN of the NRF; the address and / or FQDN of one or more fourth network elements in the core network that serve the terminal device; security parameters, and slice information, wherein the related parameters can be referred to the above.
[0153] In some implementations, the DHCP proxy network element can send the first message to the terminal device through a terminal configuration update process.
[0154] In step S340, the terminal device establishes a security context with the NRF based on the security parameters.
[0155] In step S345, the terminal device sends a fourth message to the access network device, and the fourth message includes the address of the terminal device and the identifier of the terminal device. For example, the fourth message can include the mapping relationship between the identifier of the terminal device and the address of the terminal device.
[0156] In some implementations, the identifier of the terminal device can be an identifier of the terminal device that is used by the access network device to page the terminal device. For example, the identifier of the terminal device can include a GUTI and / or a 5G-S-TMSI.
[0157] In the embodiments of the present application, the fourth message is not limited. In some implementations, the fourth message is an AS message. In this way, the access network device can obtain the address of the terminal device from the AS message, which helps to simplify the complexity of the access network device obtaining the address of the terminal device. In other implementations, the fourth message is a NAS message, for example, the fourth message can be encapsulated in a NAS container. At this time, the fourth message is transparent to the access network device, and the access network device can obtain the address of the terminal device from the core network receiving the fourth message, that is, the address of the terminal device is invisible in the air interface transmission process, which helps to improve the security of transmitting the fourth message.
[0158] In step S350, the access network device sends the fourth message to the NRF.
[0159] In step S355, the NRF stores the identifier of the terminal device and the address of the terminal device, and encapsulates the identifier of the terminal device and the address of the terminal device in a NAS container and sends it to the UDM. For example, the NRF can store the mapping relationship between the identifier of the terminal device and the address of the terminal device, and send a NAS container carrying the mapping relationship to the UDM.
[0160] In step S360, the network slice specific authentication and authorization procedure is successfully performed.
[0161] In step S365, in the terminal device configuration update procedure, the AUSF can send a first message to the terminal device.
[0162] In some implementations, the first message can include: the identifier of the terminal device, the address of the terminal device, the address of the NRF, the FQDN or IP address of other NFs serving the terminal device.
[0163] In some implementations, if the terminal device communicates using the network slice authenticated in step S360, the terminal device can use the address of the terminal device in the first message.
[0164] It should be noted that steps S360 and S365 are optional steps. Generally, they are performed in scenarios where different network slices use different addresses of the terminal device. Conversely, if the addresses of the terminal device used by different network slices are the same, steps S360 and S365 can not be performed.
[0165] With the introduction of more and more types of terminal devices in a communication system, different terminal devices have different capabilities. At this time, if the difference in capabilities between terminal devices is ignored, and communication is directly performed with a terminal device based on an address of the terminal device, communication failure can occur.
[0166] Therefore, to solve the above problem, an embodiment of the present application provides a communication method, in which a terminal device can inform a target network element whether the terminal device supports address-based signaling transmission through a fifth message, which helps the target network element to determine whether to communicate with the terminal device based on the address based on the fifth message, so as to improve the success rate of address-based communication of the terminal device. The communication method of the embodiment of the present application is described below in combination with FIG. 4. The method shown in FIG. 4 includes step S410.
[0167] In step S410, the terminal device sends a fifth message to the target network element, and the fifth message is used to indicate that the terminal device supports address-based signaling transmission, or in other words, the fifth message is used to indicate that the capability of the terminal device is to support address-based signaling transmission.
[0168] In some implementations, address-based signaling transmission can be understood as address-based signaling transmission with a core network. For example, the signaling can be control plane signaling, that is, the address of the terminal device is an address allocated by a first network element to the terminal device on the control plane, so that the terminal device can perform control plane signaling transmission based on the address. Of course, in the embodiment of the present application, the signaling can be user plane signaling.
[0169] In some implementations, the address of the terminal device can include an IP address of the terminal device and / or a MAC address of the terminal device. Taking the address of the terminal device as an example, the IP address of the terminal device can be a globally unique IPv6 address of the terminal device.
[0170] In some implementations, the address of the terminal device and the address of the access network device belong to different address sets. For example, the prefix of the IPv6 address of the terminal device is different from the prefix of the IPv6 address of the access network device, which helps other network elements to distinguish whether the source of the NAS message is the terminal device or the access network device according to the prefix of the IPv6 address.
[0171] In the embodiment of the present application, the target network element is not limited. In some implementations, the target network element can be a network element in a core network. For example, the target network element can be an AUSF and / or an AMF. In other implementations, the target network element can also be an access network device.
[0172] In some implementations, the fifth message can be sent by the terminal device to the target network element actively. In other implementations, the fifth message can be triggered by broadcast information sent by the target network element. That is, before step S410, the above method further includes: sending, by the target network element, broadcast information to the terminal device, the broadcast information being used to indicate that the target network element supports address-based transmission of signaling, or the broadcast information being used to indicate that the target network element supports address-based transmission of signaling of the terminal device.
[0173] In some implementations, the target network element can be an access network device, and correspondingly, the broadcast information can be a system information block (SIB).
[0174] In some implementations, after the terminal device sends the fifth message to the target network element, the target network element can feed back a sixth message to the terminal device. That is, the above method further includes: sending, by the target network element, the sixth message to the terminal device, wherein the sixth message is used to indicate one or more of the following: the target network element supports address-based transmission of signaling; the target network element accepts address-based transmission of signaling; the target network element does not support address-based transmission of signaling; and the target network element rejects address-based transmission of signaling.
[0175] For example, when the sixth message is used to indicate that the target network element supports address-based transmission of signaling, the sixth message is used to indicate that the target network element supports address-based transmission of signaling of the terminal device.
[0176] For example, when the sixth message is used to indicate that the target network element does not support address-based transmission of signaling, the sixth message is used to indicate that the target network element does not support address-based transmission of signaling of the terminal device.
[0177] For example, when the sixth message is used to indicate that the target network element accepts address-based transmission of signaling, the sixth message is used to indicate that the target network element accepts address-based transmission of signaling of the terminal device.
[0178] For example, when the sixth message is used to indicate that the target network element rejects (or does not accept) address-based transmission of signaling, the sixth message is used to indicate that the target network element rejects address-based transmission of signaling of the terminal device.
[0179] In some implementations, the fifth message is a registration request message, and correspondingly, the sixth message can be a registration accept message. Of course, in the embodiments of the present application, the fifth message and / or the sixth message can be other messages.
[0180] In some scenarios, if the target network element indicates support or acceptance of address-based signaling transmission through the sixth message, the target network element can request the terminal device address for the terminal device, at this time, the target network element can be the first network element introduced above, for example, the first network element can allocate the address for the terminal device by using the scheme introduced in FIG. 2. That is to say, the scheme shown in FIG. 2 can be used in combination with the scheme shown in FIG. 4, so that after the capability negotiation by using the method described in FIG. 4, the address allocation is performed by using the method shown in FIG. 2, which helps to improve the rationality of address allocation. Of course, in the embodiment of the present application, the scheme shown in FIG. 2 can be used alone with the scheme shown in FIG. 4.
[0181] For the convenience of understanding, the scheme of the terminal device, the access network device and the core network element for capability negotiation in the embodiment of the present application is introduced below in combination with FIG. 5. The method shown in FIG. 5 includes steps S510 to S550. It should be understood that the method shown in FIG. 5 is mainly introduced in the form of method flow, and the related information can be referred to the above.
[0182] In step S510, the access network device sends broadcast information, which is used to indicate that the access network device supports address-based signaling transmission, wherein the broadcast information can be, for example, SIB.
[0183] It should be noted that if the terminal devices in the communication system all support address-based signaling transmission, step S510 can be omitted.
[0184] In step S520, when the terminal device listens to the SIB and determines to access the access network device, the terminal device sends a fifth message to the access network device, and the fifth message is used to indicate that the terminal device supports address-based signaling transmission.
[0185] In some implementations, the fifth message is an RRC message, and / or the fifth message carries the identity of the terminal device.
[0186] In step S530, the access network device sends a response message 1 (as an example of the sixth message above) to the terminal device for the fifth message.
[0187] In some implementations, if the access network device determines to start address-based signaling transmission for the terminal device, the response message 1 is used to indicate one or more of the following: the access network device supports address-based signaling transmission; the access network device accepts address-based signaling transmission. Conversely, if the access network device determines not to start address-based signaling transmission for the terminal device, the response message 1 is used to indicate one or more of the following: the access network device does not support address-based signaling transmission; the access network device rejects address-based signaling transmission.
[0188] In step S540, if the access network device determines to start address-based transmission signaling for the terminal device, the terminal device sends a fifth message to the core network element 1, and the fifth message is used to indicate that the terminal device supports address-based signaling transmission. The core network element 1 may be, for example, an AUSF and / or an AMF.
[0189] In some implementations, the fifth message is an RRC message, and / or the fifth message carries an identifier of the terminal device.
[0190] In step S550, the core network element 1 sends a response message 2 (as an example of the above sixth message) to the terminal device for the fifth message.
[0191] In some implementations, the response message 2 is used to indicate one or more of the following: the core network element 1 supports address-based signaling transmission; and the core network element 1 accepts address-based signaling transmission.
[0192] In other implementations, the response message 2 is used to indicate one or more of the following: the core network element 1 does not support address-based signaling transmission; and the core network element 1 rejects address-based signaling transmission.
[0193] In some implementations, if the core network element 1 accepts address-based signaling transmission and the core network element 1 is an AUSF, the AUSF can request a DHCP server to allocate an address of the terminal device to the terminal device for signaling transmission.
[0194] As described above, some interactions between core network elements support service interfaces, but the N1 interface between the terminal device and the AMF, the N2 interface between the AN and the AMF, and the N4 interface between the SMF and the UPF still use traditional reference points for interaction. However, the service-based architecture evolution is not complete. When the terminal device, the access network device, and the core network element perform signaling interaction, the AMF must be relayed. That is, in addition to mobility management, the AMF also acts as a NAS signaling anchor point for the terminal device and other core network elements (for example, a session management function, an AUSF, etc.), which means that the AMF must also participate in session management and security management support (for example, identity verification, encryption / decryption), so the AMF has a higher probability of failure compared to other core network functions due to the more functions supported by the AMF. Once the AMF fails, it will seriously affect the communication between the terminal device and other core network elements.
[0195] Therefore, the embodiments of the present application provide a communication method to solve the above problems. In the method, a terminal device can transmit NAS signaling based on an address of the terminal device. That is, in the solution, the AMF is no longer an anchor point for the terminal device to perform signaling transmission with the core network. Compared with the traditional solution in which the AMF is an anchor point for the terminal device to perform signaling transmission with the core network, the AMF failure has less impact on the communication between the terminal device and other core network elements.
[0196] In some implementations, the transmission of the NAS signaling based on the address can be understood as the transmission of the NAS signaling between the terminal device and the core network based on the address of the terminal device. For example, the NAS signaling can be control plane signaling. That is, the address of the terminal device is an address allocated to the terminal device by a first network element on the control plane, so that the terminal device can perform transmission of the control plane signaling based on the address. Of course, in the embodiments of the present application, the NAS signaling can be user plane signaling.
[0197] In some implementations, the address of the terminal device can include an IP address of the terminal device and / or a MAC address of the terminal device. For example, the address of the terminal device includes the IP address of the terminal device, and the IP address of the terminal device can be a globally unique IPv6 address of the terminal device.
[0198] In some implementations, the address of the terminal device and the address of the access network device belong to different address sets. For example, the prefix of the IPv6 address of the terminal device is different from the prefix of the IPv6 address of the access network device, which helps other network elements to distinguish whether the source of the NAS message is the terminal device or the access network device according to the prefix of the IPv6 address.
[0199] The transmission solutions of the NAS signaling in the mobile original (MO) scenario and the mobile terminated (MT) scenario are described below in combination with FIGS. 6 to 14B.
[0200] It should be understood that the communication process introduced below in connection with scenario 1 and scenario 2 can be used independently of the schemes introduced above in connection with FIG. 2 and FIG. 4. Alternatively, the communication process introduced below in connection with scenario 1 and scenario 2 can be used in combination with the schemes introduced above in connection with FIG. 2 and FIG. 4. For example, the communication process introduced in scenario 1 and / or scenario 2 can be used in combination with the scheme shown in FIG. 2, in which case the address of the terminal device involved in scenario 1 and / or scenario 2 can be configured by the method described in FIG. 2, and in this case, the terminal device can perform signaling transmission with the core network based on the address of the terminal device, that is, in this scheme, the AMF is no longer an anchor point for the terminal device to perform signaling transmission with the core network, which helps to reduce the impact of AMF failure on communication between the terminal device and other core network elements compared to the traditional scheme in which the AMF is an anchor point for the terminal device to perform signaling transmission with the core network. For another example, the communication process introduced in scenario 1 and / or scenario 2 can be used in combination with the scheme shown in FIG. 4, in which case the capability negotiation can be performed by the method described in FIG. 4 before the communication process involved in scenario 1 and / or scenario 2 is performed, which helps to improve the rationality of communication in scenario 1 and / or scenario 2.
[0201] Scenario 1: MO scenario.
[0202] FIG. 6 is a schematic flowchart of a communication method according to an embodiment of the present application. The method shown in FIG. 6 includes step S610. In step S610, the terminal device sends a seventh message to the access network device.
[0203] In some implementations, the seventh message contains one or more of the following: first NAS signaling; an address of the terminal device; an address of the fourth network element.
[0204] Taking the example that the seventh message includes the first NAS signaling, the first NAS signaling is NAS signaling sent by the terminal device to the fourth network element in the core network. In some implementations, the seventh message contains a first NAS container, and the first NAS signaling is carried in the first NAS container. In other implementations, the seventh message is an RRC message.
[0205] Taking the example that the seventh message includes the address of the terminal device, the address of the terminal device can include an IP address of the terminal device and / or a MAC address of the terminal device, which helps the access network device to determine which terminal device sends the seventh message.
[0206] Taking the example that the seventh message includes the address of the fourth network element, the address of the fourth network element can include an IP address of the fourth network element and / or a MAC address of the fourth network element, which helps the access network device to determine the receiving end of the seventh message.
[0207] In some embodiments, after receiving the seventh message, the access network device can send the first NAS signaling to the fourth network element through a first data packet. That is, the above method further includes: after receiving the seventh message, the access network device sends a first data packet to the fourth network element, and the first data packet contains the first NAS signaling (also referred to as MO signaling).
[0208] In some embodiments, the first data packet is a data packet transmitted based on an address. For example, the address is an IP address of the terminal device, and the first data packet is an IP data packet.
[0209] In some embodiments, the first data packet includes one or more of the following: an address of the access network device, an address of the fourth network element, and an address of the terminal device. The address of the access network device is used by the fourth network element to identify which access network device the first data packet comes from, the address of the terminal device is used by the fourth network element to identify which terminal device the first data packet comes from, and the address of the fourth network element is used by the fourth network element to identify the receiving end of the first data packet.
[0210] In some embodiments, the address of the access network device can include an IP address and / or a MAC address of the access network device. In addition, the address of the access network device and the address of the terminal device are described above.
[0211] In the embodiments of the present application, the encapsulation manner of the above information in the first data packet is not limited. In some embodiments, the first data packet includes a first packet header and / or a second packet header. The source address of the first packet header is the address of the access network device, the destination address of the first packet header is the address of the fourth network element, the source address of the second packet header is the address of the terminal device, and the destination address of the second packet header is the address of the fourth network element.
[0212] In some embodiments, referring to FIG. 7, the first packet header can be an outer packet header (also referred to as a layer 1 packet header) of the first data packet. Correspondingly, the second packet header can be an inner packet header (also referred to as a layer 2 packet header) of the first data packet. At this time, the inner packet header and the first NAS signaling can be understood as a payload of the outer packet header, and the payload of the inner packet header is the first NAS signaling.
[0213] In some scenarios, after receiving the first data packet, the fourth network element can feed back a second data packet to the access network device. That is, the above method further includes: the fourth network element sends a second data packet to the access network device.
[0214] In some embodiments, the second data packet is a data packet transmitted based on an address. For example, the address is an IP address of the terminal device, and the second data packet is an IP data packet.
[0215] In some embodiments, the second data packet comprises second NAS signaling, the second NAS signaling being NAS signaling sent by the fourth network element in response to the first NAS signaling.
[0216] In some embodiments, the second data packet comprises one or more of the following: an address of the access network device, an address of the fourth network element, and an address of the terminal device. The address of the access network device is used by the terminal device to identify which access network device the second data packet comes from, the address of the terminal device is used by the terminal device to identify the receiving end of the second data packet, and the address of the fourth network element is used by the terminal device to identify which network element the second data packet comes from. In addition, the address of the access network device, the address of the terminal device, and the address of the fourth network element are described above.
[0217] In the embodiments of the present application, the encapsulation manner of the above information in the second data packet is not limited. In some embodiments, the second data packet comprises a third packet header and / or a fourth packet header, the source address of the third packet header is the address of the fourth network element, the destination address of the third packet header is the address of the access network device, the source address of the fourth packet header is the address of the fourth network element, and the destination address of the fourth packet header is the address of the terminal device.
[0218] In some embodiments, referring to FIG. 8, the third packet header can be an outer packet header (also referred to as a layer 1 packet header) of the second data packet, and correspondingly, the fourth packet header can be an inner packet header (also referred to as a layer 2 packet header) of the second data packet. At this time, the inner packet header and the second NAS signaling can be understood as the payload of the outer packet header, and the payload of the inner packet header is the second NAS signaling.
[0219] In some embodiments, if the access network device receives the second data packet, the access network device can send the second NAS signaling to the terminal device. That is, the above method further comprises: the access network device sending an eighth message to the terminal device, the eighth message comprising the second NAS signaling.
[0220] In some embodiments, the eighth message further comprises the address of the terminal device and / or the address of the fourth network element, wherein the address of the terminal device helps the terminal device to confirm the receiving end of the eighth message, and the address of the fourth network element helps the terminal device to confirm the sending end of the eighth message.
[0221] In some embodiments, the eighth message comprises a second NAS container, and the second NAS signaling is carried in the second NAS container. In other embodiments, the eighth message is an RRC message.
[0222] In some scenarios, the terminal device can learn the address of the fourth network element before sending the seventh message, at this time, the terminal device can communicate with the fourth network element through the access network device according to the scheme introduced above. However, in some other scenarios, the terminal device cannot obtain the address of the fourth network element, at this time, the terminal device cannot directly communicate with the fourth network element. Therefore, to solve the above problems, the embodiment of the present application further provides a communication method, in which the terminal device can request the address of the fourth network element from the third network element. The third network element can have a function of discovering other network elements, for example, the third network element can be an NRF. Of course, in the embodiment of the present application, the third network element can also be a network element having the same or similar function in a future communication system.
[0223] That is to say, before step S610, the above method further includes: the terminal device sends a ninth message to the access network device, the ninth message containing first information, the first information being used to request the address of the fourth network element from the third network element of the core network; and / or the access network device sends a third data packet to the third network element, the third data packet being a data packet based on address transmission, and the third data packet containing the first information.
[0224] In some scenarios, the first information is used to request the address of the fourth network element, therefore, the first information can also be called address request or network element IP address request.
[0225] In some implementations, the ninth message contains a third NAS container, and the first information is carried in the third NAS container, which helps to directly deliver the first information to the target endpoint, avoids reading by the intermediate node transmitting the ninth message, and helps to improve the security of information transmission. In some other implementations, the third NAS container can also be encrypted to improve the security of transmission of the first information. In some other implementations, the ninth message can be an RRC message.
[0226] In some implementations, the first information contains one or more of the following: an identifier of the terminal device; a type of the fourth network element; an FQDN of the fourth network element; slice information.
[0227] Taking the first information including the identifier of the terminal device as an example, the identifier of the terminal device is used for the third network element to discover the fourth network element serving the terminal device. In the embodiment of the present application, the identifier of the terminal device can include one or more of the following: SUPI, SUCI, GPSI.
[0228] Taking the first information including the type of the fourth network element as an example, the type of the fourth network element can be understood as the function of the fourth network element, accordingly, the third network element can determine the fourth network element requested to be discovered by the terminal device based on the type of the fourth network element. Taking the fourth network element as an AMF as an example, the type of the fourth network element is AMF.
[0229] Taking an example in which the first information includes the FQDN of the fourth network element, the third network element can query the address of the fourth network element based on the FQDN of the fourth network element. For example, the NRF can determine the address of the fourth network element based on a mapping relationship between the FQDN of the fourth network element and the address of the fourth network element stored locally. For another example, the NRF can query the address of the fourth network element from a server (for example, a DHCP server) based on the FQDN of the fourth network element.
[0230] In some scenarios, the number of fourth network elements requested to be discovered by the terminal device can include one or more. If the number of fourth network elements requested to be discovered by the terminal device can be multiple, the first information can carry a list to indicate the multiple fourth network elements requested to be discovered by the terminal device.
[0231] Taking an example in which the first information includes slice information, the slice information can be the slice information of the terminal device, so that the third network element discovers the fourth network element corresponding to the slice information for the terminal device. The fourth network element corresponding to the slice information can be understood as the fourth network element that can communicate with the terminal device through the network slice indicated by the slice information. For example, the slice information can be S-NSSAI.
[0232] In some implementations, the ninth message further includes the address of the terminal device and / or the address of the third network element. The address of the terminal device included in the ninth message can be used as the target address of the information indicating the address of the fourth network element when the third network element indicates the address of the fourth network element to the terminal device.
[0233] In some implementations, the address of the terminal device and / or the address of the third network element can be located outside the third NAS container.
[0234] In some implementations, the third data packet further includes one or more of the following: the address of the access network device; the address of the third network element; and the address of the terminal device. For example, the address can include a MAC address and / or an IP address.
[0235] In the embodiments of the present application, the encapsulation manner of the above information in the third data packet is not limited. In some implementations, the third data packet includes a fifth packet header and / or a sixth packet header. The source address of the fifth packet header is the address of the access network device, the destination address of the fifth packet header is the address of the third network element, the source address of the sixth packet header is the address of the terminal device, and the destination address of the sixth packet header is the address of the third network element.
[0236] In some implementations, referring to FIG. 9, the fifth packet header can be an outer packet header (also referred to as a layer 1 packet header) of the third data packet, and correspondingly, the sixth packet header can be an inner packet header (also referred to as a layer 2 packet header) of the third data packet. At this time, the inner packet header and the first information can be understood as the payload of the outer packet header, and the payload of the inner packet header is the first information.
[0237] The above describes a scheme in which the terminal device requests the address of the fourth network element from the third network element, and the following describes a scheme in which the third network element feeds back the address of the fourth network element to the terminal device.
[0238] In some implementations, the method further includes: sending, by the third network element, a fourth data packet to the access network device, the fourth data packet being a data packet transmitted based on the address.
[0239] In some implementations, the fourth data packet contains one or more of the following: the address of the fourth network element; the FQDN of the fourth network element; the type of the fourth network element; the identifier of the terminal device; the address of the terminal device; the address of the access network device; and the slice information.
[0240] Taking the fourth data packet containing the address of the fourth network element as an example, it is helpful for the terminal device to communicate with the fourth network element based on the address of the fourth network element. The address of the fourth network element can be found in the foregoing description.
[0241] Taking the fourth data packet containing the FQDN of the fourth network element as an example, the terminal device can request the address of the fourth network element from a server based on the FQDN of the fourth network element, where the server can be a DHCP server for example.
[0242] Taking the fourth data packet containing the type of the fourth network element as an example, the type of the fourth network element can be understood as the function of the fourth network element.
[0243] In some implementations, if the fourth data contains the type of the fourth network element and the address of the fourth network element, the type of the fourth network element and the address of the fourth network element can be carried in the fourth data in a mutually associated manner. For example, the mutually associated manner can be represented by a list, i.e., list[type of fourth network element; address of fourth network element]. Taking the fourth network element as an AMF as an example, the mutually associated manner can be identified as list[AMF; address of AMF].
[0244] In other implementations, if the fourth data contains the type of the fourth network element and the FQDN of the fourth network element, the type of the fourth network element and the FQDN of the fourth network element can be carried in the fourth data in a mutually associated manner. For example, the mutually associated manner can be identified as list[type of fourth network element; FQDN of fourth network element]. Taking the fourth network element as an AMF as an example, the mutually associated manner can be identified as list[SMF; FQDN of SMF].
[0245] Taking the fourth data packet containing the identifier of the terminal device as an example, the identifier of the terminal device is used to identify the terminal device, and the description of the identifier of the terminal device can be found in the foregoing description.
[0246] For example, the fourth data packet includes the address of the terminal device, which helps the access network device to determine the receiving end of the fourth data packet. The address of the terminal device can be found in the foregoing description.
[0247] For example, the fourth data packet includes the address of the access network device, which helps the access network device to determine that the receiving end of the fourth data packet is the access network device. The address of the access network device can be found in the foregoing description.
[0248] For example, the fourth data packet includes the slice information, which helps the terminal device to determine the used slice. In some scenarios, the terminal device can use different addresses of the terminal device when communicating based on different network slices. Therefore, carrying the slice information in the fourth data packet helps the terminal device to determine the network slice to which the address of the terminal device is applicable. The slice information can be, for example, S-NSSAI.
[0249] In the embodiments of the present application, the encapsulation manner of the above information in the fourth data packet is not limited. In some implementations, the fourth data packet includes a seventh packet header and / or an eighth packet header, the source address of the seventh packet header is the address of the third network element, the destination address of the seventh packet header is the address of the access network device, the source address of the eighth packet header is the address of the third network element, and the destination address of the eighth packet header is the address of the terminal device.
[0250] In some implementations, the one or more types of information carried in the fourth data packet introduced above can be referred to as an "NF address response message". Referring to FIG. 10, the seventh packet header can be the outer packet header (also referred to as layer 1 packet header) of the fourth data packet, and correspondingly, the eighth packet header can be the inner packet header (also referred to as layer 2 packet header) of the fourth data packet. At this time, the inner packet header and the NF address response message can be understood as the payload of the outer packet header, and the payload of the inner packet header is the NF address response message.
[0251] In some scenarios, after receiving the fourth data packet, the access network device can not know the identity of the terminal device corresponding to the address of the terminal device, and at this time, the access network device can not be able to forward the fourth data packet to the corresponding terminal device. In this case, the access network device can request the identity of the terminal device from a fifth network element in the core network, where the fifth network element can be a network element that stores the identity of the terminal device corresponding to the address of the terminal device, for example, the fifth network element can be a network element that stores the mapping relationship between the address of the terminal device and the identity of the terminal device. For example, the fifth network element can be one or more of NRF, UDM, and AMF.
[0252] That is to say, the method further includes: the access network device sending second information to the fifth network element of the core network, the second information being used for requesting the identifier of the terminal device, and the second information containing the address of the terminal device; and the access network device receiving the identifier of the terminal device sent by the fifth network element.
[0253] In some implementations, if the access network device obtains the identifier of the terminal device, the access network device can forward part or all of the information in the fourth data packet to the terminal device through the tenth message. That is to say, the method further includes: the access network device sending the tenth message to the terminal device, wherein the tenth message contains one or more of the following: the address of the fourth network element; the FQDN of the fourth network element; the type of the fourth network element; the identifier of the terminal device; and the address of the terminal device. The related descriptions of the information in the tenth message can be referred to the above.
[0254] In some implementations, the tenth message contains a fourth NAS container, and the address of the fourth network element is carried in the fourth NAS container. In other implementations, the tenth message is an RRC message.
[0255] It should be noted that the address of the terminal device and / or the identifier of the terminal device in the tenth message can be in the fourth NAS container, or the address of the terminal device and / or the identifier of the terminal device in the tenth message can be outside the fourth NAS container. Of course, in the embodiments of the present application, the address of the terminal device and / or the identifier of the terminal device in the tenth message can be both in the fourth NAS container and outside the fourth container.
[0256] For ease of understanding, the third network element and the fifth network element are taken as NRF, and the fourth network element is taken as NF1 as an example, and the process of communication between the terminal device and the core network in the MO scenario of the embodiments of the present application is introduced in combination with FIG. 11. The method shown in FIG. 11 includes steps S1110 to S1160. It should be understood that the method shown in FIG. 11 mainly introduces the method flow, and the related information can be referred to the above.
[0257] In step S1110, when there is MO signaling to be sent to the NF, the terminal device sends a ninth message to the access network device, and the ninth message contains first information, the first information being used for requesting the address of the fourth network element from the third network element of the core network; and / or the access network device sends a third data packet to the third network element, the third data packet being a data packet based on address transmission, and the third data packet containing the first information.
[0258] In some implementations, the first information contains one or more of the following: the identifier of the terminal device; the type of the fourth network element; the FQDN of the fourth network element; and slice information.
[0259] In some embodiments, the ninth message contains a third NAS container, and the first information is carried in the third NAS container, which helps to directly deliver the first information to the target endpoint, avoids reading by an intermediate node transmitting the ninth message, and helps to improve the security of information transmission. In some other embodiments, the third NAS container can also be encrypted to improve the security of the first information transmission. In some other embodiments, the ninth message can be an RRC message.
[0260] In some embodiments, the ninth message further includes an address of the terminal device and / or an address of the third network element. In some embodiments, the ninth message is an RRC message.
[0261] In step S1115, the access network device sends a third packet to the NRF, the third packet is an address-based packet, and the third packet contains the first information.
[0262] In some embodiments, the third packet further includes one or more of the following: an address of the access network device; an address of the third network element; an address of the terminal device.
[0263] In some embodiments, the access network device extracts the NAS container from the RRC message and encapsulates it into one or more third packets. The third packet can include the packet headers of two different layers, as shown in FIG. 9.
[0264] In step S1120, the NRF determines NF1 serving the terminal device based on the identifier of the terminal device.
[0265] In some embodiments, if the NRF finds multiple candidate NFs, the NRF can select the NF closest to the terminal device as NF1 based on the type of the target NF requested.
[0266] In step S1125, the NRF sends a fourth packet to the access network device, and the fourth packet is an address-based packet.
[0267] In some embodiments, the fourth packet contains one or more of the following: an address of NF1; an FQDN of NF1; a type of NF1; an address of the terminal device; an address of the access network device; slice information.
[0268] In some embodiments, the fourth packet includes a seventh packet header and / or an eighth packet header, the source address of the seventh packet header is the address of the NRF, the destination address of the seventh packet header is the address of the access network device, the source address of the eighth packet header is the address of the NRF, and the destination address of the eighth packet header is the address of the terminal device, as shown in FIG. 10.
[0269] It should be noted that if the terminal device has obtained the FQDN of the NF1 or the address of the NF1 in the previous interaction with the core network, steps S1110 to S11130 can be skipped.
[0270] In step S1130, the access network device sends second information to the NRF, the second information is used to request the identifier of the terminal device, and the second information contains the address of the terminal device.
[0271] In some implementations, after receiving the fourth data packet, the access network device extracts the NF IP address response from the payload of the fourth data packet, and determines that the response message is to be sent to the terminal device according to the target address contained in the eighth packet header of the fourth data packet. If the access network device does not save the mapping relationship between the identifier of the terminal device and the address of the terminal device, the access network device can obtain the identifier of the terminal device from a core network element (such as NRF, UDM, AMF, etc.) that stores the mapping relationship. For example, the access network device sends a terminal device address query request (as an example of the second information) to the NRF to query the identifier of the terminal device, wherein the terminal device address query request carries the address of the terminal device.
[0272] It should be noted that if the terminal device has obtained the FQDN of the NF1 or the address of the NF1 in the previous interaction with the core network, steps S1110 to S11130 can be skipped.
[0273] In step S1135, the NRF sends the identifier of the terminal device to the access network device.
[0274] It should be noted that if the identifier of the terminal device is carried in step S1125, the access network device can not perform steps S1130 and S1135.
[0275] In step S1140, the access network device sends a tenth message to the terminal device, wherein the tenth message contains one or more of the following: the address of the NF1; the FQDN of the NF1; the type of the NF1; the identifier of the terminal device; and the address of the terminal device.
[0276] In some implementations, the tenth message contains a fourth NAS container, and the address of the NF1 is carried in the fourth NAS container. In other implementations, the tenth message is an RRC message.
[0277] It should be noted that the address of the terminal device and / or the identifier of the terminal device in the tenth message can be in the fourth NAS container, or the address of the terminal device and / or the identifier of the terminal device in the tenth message can be outside the fourth NAS container. Of course, in the embodiments of the present application, the address of the terminal device and / or the identifier of the terminal device in the tenth message can be both in the fourth NAS container and outside the fourth container.
[0278] In step S1145, the terminal device sends a seventh message to the access network device, and the seventh message contains one or more of the following: the first NAS signaling; the address of the terminal device; the address of the NF1.
[0279] In some implementations, the seventh message is an RRC message.
[0280] In step S1150, after receiving the seventh message, the access network device sends a first data packet to the NF1, and the first data packet contains the first NAS signaling (i.e., the MO signaling in the foregoing).
[0281] In some implementations, the first data packet includes one or more of the following: the address of the access network device; the address of the NF1; the address of the terminal device.
[0282] In some implementations, the first data packet includes a first packet header and / or a second packet header, the source address of the first packet header is the address of the access network device, the destination address of the first packet header is the address of the NF1, the source address of the second packet header is the address of the terminal device, and the destination address of the second packet header is the address of the NF1, see FIG. 7.
[0283] In step S1155, the NF1 sends a second data packet to the access network device.
[0284] In some implementations, the second data packet contains the second NAS signaling, and the second NAS signaling is the NAS signaling sent by the NF1 in response to the first NAS signaling.
[0285] In some implementations, the second data packet includes one or more of the following: the address of the access network device, the address of the NF1, and the address of the terminal device, wherein the address of the terminal device can be obtained from step S1150.
[0286] In some implementations, the second data packet includes a third packet header and / or a fourth packet header, the source address of the third packet header is the address of the NF1, the destination address of the third packet header is the address of the access network device, the source address of the fourth packet header is the address of the NF1, and the destination address of the fourth packet header is the address of the terminal device, see FIG. 8.
[0287] In step S1160, the access network device sends an eighth message to the terminal device, and the eighth message contains the second NAS signaling.
[0288] In some implementations, the eighth message further includes the address of the terminal device and / or the address of the NF1.
[0289] In some implementations, the eighth message contains a second NAS container, and the second NAS signaling is carried in the second NAS container. In other implementations, the eighth message is an RRC message.
[0290] Scenario 2: MT scenario
[0291] FIG. 12 is a schematic flowchart of a communication method according to an embodiment of the application. The method shown in FIG. 12 includes step S1210.
[0292] In step S1210, a fourth network element in the core network sends a fifth data packet to the access network device, the fifth data packet is a data packet based on address transmission, and the fifth data packet contains third NAS signaling, the third NAS signaling is NAS signaling (also referred to as MT signaling) sent by the fourth network element to the terminal device.
[0293] In some implementations, if the address is an IP address, the fifth data packet is an IP data packet.
[0294] In some implementations, the fourth network element is a network element that provides services for the terminal device, for example, the fourth network element can be a mobility management network element, a session management network element, etc. It should be understood that the fourth network element can be any of the network elements introduced above, or can be other network elements introduced in future communication systems.
[0295] In some implementations, the fifth data packet further includes one or more of the following: an address of the fourth network element; an address of the terminal device; an address of the access network device; slice information.
[0296] Taking an example that the fifth data packet includes the address of the fourth network element, it is helpful for the terminal device to communicate with the fourth network element based on the address of the fourth network element. The address of the fourth network element can include an IP address of the fourth network element and / or a MAC address of the fourth network element.
[0297] Taking an example that the fifth data packet includes the address of the terminal device, it is helpful for the access network device to determine the receiving end of the fifth data packet. The address of the terminal device can include an IP address of the terminal device and / or a MAC address of the terminal device.
[0298] Taking an example that the fifth data packet includes the address of the access network device, it is helpful for the access network device to determine that the receiving end of the fifth data packet is the access network device. The address of the access network device can include an IP address of the access network device and / or a MAC address of the access network device.
[0299] For example, the fifth data packet includes slice information, which helps the terminal device to determine the used slice. In some scenarios, the terminal device uses different addresses of the terminal device when communicating based on different network slices. Therefore, carrying the slice information in the fifth data packet helps the terminal device to determine the network slice to which the address of the terminal device applies. The slice information may be, for example, S-NSSAI.
[0300] In the embodiments of the present application, the encapsulation manner of the above information in the fifth data packet is not limited. In some implementations, the fifth data packet includes a ninth packet header and / or a tenth packet header, the source address of the ninth packet header is the address of the fourth network element, the destination address of the ninth packet header is the address of the access network device, the source address of the tenth packet header is the address of the fourth network element, and the destination address of the tenth packet header is the address of the terminal device.
[0301] In some implementations, referring to FIG. 13, the ninth packet header can be an outer packet header (also referred to as a layer 1 packet header) of the fifth data packet, and correspondingly, the tenth packet header can be an inner packet header (also referred to as a layer 2 packet header) of the fifth data packet. At this time, the inner packet header and the third NAS signaling can be understood as the payload of the outer packet header, and the payload of the inner packet header is the third NAS signaling.
[0302] In some implementations, the access network device can send the third NAS signaling of the fifth data packet to the terminal device through an eleventh message. That is, the above method further includes: the access network device sends an eleventh message to the terminal device, and the eleventh message contains one or more of the following: the third NAS signaling; the address of the fourth network element; and the address of the terminal device. The above information can be referred to the above description.
[0303] In some implementations, the fifth NAS container contained in the eleventh message, and the third NAS signaling is carried in the fifth NAS container. Correspondingly, the address of the fourth network element and the address of the terminal device can be located outside the third NAS signaling. In another implementation, the eleventh message is an RRC message.
[0304] In some scenarios, the terminal device can be in an idle state, and at this time, before the access network device sends the eleventh message to the terminal device, the access network device needs to page the terminal device. That is, before the access network device sends the eleventh message to the terminal device, the above method further includes: if the terminal device is in an idle state, the access network device sends a paging message to the terminal device, and the paging message contains the identifier of the terminal device.
[0305] Of course, in the embodiment of the present application, the paging message for the terminal device described above can be initiated by a network element (for example, the fourth network element) in the core network, for example, see the method shown in FIG. 14B. Accordingly, the paging message can be made before the fourth network element sends the fifth data packet. Of course, in the embodiment of the present application, the paging message can be made after the fourth network element sends the fifth data packet to the access network device. At this time, the access network device can first store the fifth data packet, and send the eleventh message corresponding to the fifth data packet to the terminal device after the connection between the terminal device and the fourth network element is successfully established.
[0306] In other scenarios, the fourth network element can not know the information of the access network device serving the terminal device, at this time, the fourth network element cannot determine the access network element receiving the fifth data packet. At this time, the fourth network element can request the address of the access network device from the second network element. In still other scenarios, the fourth network element can not know the information of the terminal device, at this time, the fourth network element can request the address of the terminal device from the second network element. Wherein, the second network element includes UDM and / or UDR.
[0307] That is to say, before the fourth network in the core network sends the fifth data packet to the access network device, the above method further includes: the fourth network element sends a twelfth message to the second network element in the core network, the twelfth message is used to request the address of the terminal device and / or the address of the access network device.
[0308] In some implementations, if the twelfth message is used to request the address of the terminal device or the address of the access network device, the twelfth message contains the identifier of the terminal device, wherein the identifier of the terminal device includes one or more of the following: SUPI, SUCI, GPSI.
[0309] In other implementations, the twelfth message is used to request the address of the access network device, and the twelfth message contains the identifier of the terminal device and / or the address of the terminal device.
[0310] In some implementations, the above method further includes: the second network element sends a thirteenth message to the fourth network element, the thirteenth message contains one or more of the following: the address of the access network device; the identifier of the access network device; the identifier of the terminal device, wherein the address of the access network device includes the IP address or the MAC address of the access network device.
[0311] For ease of understanding, hereinafter, the fourth network element is taken as NF1 and the second network element is taken as UDM as an example, the process of communication between the terminal device and the core network in the MT scenario of the embodiment of the present application is introduced in combination with FIG. 14A and FIG. 14B. It is assumed that the NF1 does not know the access network device serving the terminal device. The method shown in FIG. 14A includes steps S1410 to S1460. It should be understood that the method shown in FIG. 14A mainly introduces the method flow, and the introduction of related information can be referred to the above.
[0312] In step S1410, the NF1 sends a twelfth message to the UDM, the twelfth message being used for requesting an address of the access network device providing service for the terminal device.
[0313] In some implementations, the twelfth message contains an identity of the terminal device and an address of the terminal device, wherein the identity of the terminal device comprises one or more of the following: SUPI, SUCI, GPSI.
[0314] In step S1420, the UDM sends a thirteenth message to the NF1, the thirteenth message being used for requesting the address of the access network device.
[0315] In some implementations, the thirteenth message contains one or more of the following: the address of the access network device; an identity of the access network device; an identity of the terminal device, wherein the address of the access network device comprises an IP address or a MAC address of the access network device.
[0316] In step S1430, the NF1 sends a fifth data packet to the access network device, the fifth data packet being a data packet transmitted based on the address, and the fifth data packet containing a third NAS signaling, the third NAS signaling being a NAS signaling sent by the fourth network element to the terminal device.
[0317] In some implementations, the fifth data packet further comprises one or more of the following: an address of the fourth network element; an address of the terminal device; an address of the access network device; slice information, for details of the related information, please refer to the above.
[0318] In some implementations, the fifth data packet comprises a ninth packet header and / or a tenth packet header, a source address of the ninth packet header being an address of the NF1, a destination address of the ninth packet header being an address of the access network device, a source address of the tenth packet header being an address of the NF1, and a destination address of the tenth packet header being an address of the terminal device, for details, please refer to FIG. 13.
[0319] In step S1440, if the terminal device is in an idle state, the access network device sends a paging message to the terminal device, the paging message containing an identity of the terminal device.
[0320] In some implementations, the access network device extracts the third NAS signaling from a payload of the fifth data packet, and can determine the terminal device to which the third NAS signaling needs to be sent according to the tenth packet header.
[0321] In step S1450, an AS connection is successfully established between the terminal device and the access network device.
[0322] It should be noted that if the terminal device is in a connected state, steps S1240 and S1250 can not be performed.
[0323] In step S1460, the access network device sends a eleventh message to the terminal device, and the eleventh message contains one or more of the following: the third NAS signaling; the address of the NF1; and the address of the terminal device. For details of the above information, refer to the foregoing description.
[0324] In some implementations, the eleventh message contains a fifth NAS container, and the third NAS signaling is carried in the fifth NAS container. Accordingly, the address of the NF1 and the address of the terminal device can be located outside the third NAS signaling. In other implementations, the eleventh message is an RRC message.
[0325] The method shown in FIG. 14B includes steps S1510 to S1580. It should be understood that the method shown in FIG. 14B mainly introduces the method flow, and for related information, refer to the foregoing description.
[0326] In step S1510, the NF1 sends a twelfth message to the UDM, and the twelfth message is used to request the address of the access network device that provides services for the terminal device.
[0327] In some implementations, the twelfth message contains the identity of the terminal device and the address of the terminal device, wherein the identity of the terminal device includes one or more of the following: SUPI, SUCI, and GPSI.
[0328] In step S1520, the UDM sends a thirteenth message to the NF1, and the thirteenth message is used to request the address of the access network device.
[0329] In some implementations, the thirteenth message contains one or more of the following: the address of the access network device; the identity of the access network device; and the identity of the terminal device, wherein the address of the access network device includes the IP address or the MAC address of the access network device.
[0330] In step S1530, the NF1 sends a paging message to the access network device for paging the terminal device.
[0331] In step S1540, the access network device sends a paging message to the terminal device for paging the terminal device.
[0332] It should be noted that if the terminal device is in the connected state, steps S1530 and S1540 can not be performed.
[0333] In step S1550, the AS connection between the terminal device and the access network device is successfully established.
[0334] In step S1560, the IP layer connection between the terminal device and the NF1 is successfully established, and the security context is successfully established.
[0335] In some implementations, the terminal device and the NF1 successfully establish a security context, where the security context can be established based on security parameters. For the security parameters, refer to the description above (e.g., the security parameters involved in the scheme shown in FIG. 2).
[0336] In step S1570, the NF1 sends a fifth data packet to the access network device, where the fifth data packet is a data packet transmitted based on an address, and the fifth data packet contains the third NAS signaling, which is the NAS signaling sent by the fourth network element to the terminal device.
[0337] In some implementations, the fifth data packet further includes one or more of the following: the address of the fourth network element; the address of the terminal device; the address of the access network device; and slice information. For the related information, refer to the description above.
[0338] In some implementations, the fifth data packet includes a ninth packet header and / or a tenth packet header, where the source address of the ninth packet header is the address of the NF1, the destination address of the ninth packet header is the address of the access network device, the source address of the tenth packet header is the address of the NF1, and the destination address of the tenth packet header is the address of the terminal device. For details, refer to FIG. 13.
[0339] In step S1580, the access network device sends an eleventh message to the terminal device, where the eleventh message contains one or more of the following: the third NAS signaling; the address of the NF1; and the address of the terminal device. For the above information, refer to the description above.
[0340] In some implementations, the eleventh message contains a fifth NAS container, and the third NAS signaling is carried in the fifth NAS container. Accordingly, the address of the NF1 and the address of the terminal device can be located outside the third NAS signaling. In some other implementations, the eleventh message is an RRC message.
[0341] The above describes the method flow in the embodiments of the present application in combination with FIGS. 1 to 14B. The embodiments of the present application also provide two protocol stacks to support the transmission of the information described above. The two protocol stacks are described below in combination with FIGS. 15 and 16, respectively.
[0342] Referring to FIG. 15, the protocol stack of the terminal device includes a NAS layer and a 5G-AN protocol layer. Accordingly, the protocol layer in the protocol stack of the access network device that communicates with the terminal device is the 5G-AN protocol layer. The protocol layer in the protocol stack of the access network device that communicates with the NF in the core network includes a transport layer, an internal IP layer, an IP layer, layer 2, and layer 1. Accordingly, the protocol layer in the NF includes a NAS layer, a transport layer, an internal IP layer, layer 2, and layer 1, where the NAS layer is used to communicate with the terminal device.
[0343] Referring to FIG. 16, the protocol stack of the terminal device includes a NAS layer, an IP layer, and a 5G-AN protocol layer. Accordingly, the protocol layers in the protocol stack of the access network device that communicate with the terminal device include the 5G-AN protocol layer and the IP layer. The protocol layers in the protocol stack of the access network device that communicate with the NFs in the core network include a transport layer, an internal IP layer, an IP layer, layer 2, and layer 1, where layer 2 and layer 1 are also referred to as lower layers. Accordingly, the protocol layers in the NFs include a NAS layer, a transport layer, an internal IP layer, an IP layer, layer 2, and layer 1, where the NAS layer is used to communicate with the terminal device.
[0344] The difference between the protocol stack shown in FIG. 15 and the protocol stack shown in FIG. 16 is whether a new IP layer is added between the terminal device and the access network device. Taking the first information in the method shown in FIG. 6 as an example, the message in the NAS container is not perceivable by the access network device. Therefore, in addition to the fact that the first information in the NAS container includes the identifier of the terminal device, the address of the terminal device, and the address of the third network element, the RRC message carrying the first information can still include the identifier of the terminal device, the address of the terminal device, and the address of the third network element outside the NAS container.
[0345] In some scenarios, if the protocol stack shown in FIG. 15 is used, the structure of the RRC message is: RRC message{identifier of the terminal device, address of the terminal device, address of the third network element, NAS container [identifier of the terminal device, address of the terminal device, address of the third network element, first information]}; where the information in the NAS container is not perceivable by the access network device.
[0346] In some scenarios, if the protocol stack shown in FIG. 16 is used, an IP layer container can be introduced in the RRC message, and accordingly, the structure of the RRC message carrying the first information is: RRC message{identifier of the terminal device, IP layer container [packet header of the IP packet (address of the terminal device, address of the third network element, identifier of the terminal device NAS layer), payload of the IP packet is [first information]}, where the packet header of the IP packet is not perceivable by the lower processing unit, and the payload of the IP packet is not perceivable by the access network device.
[0347] The method embodiments of the present application are described in detail above in combination with FIGS. 1 to 16, and the device embodiments of the present application are described in detail below in combination with FIGS. 17 to 30. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and therefore, the parts not described in detail can be referred to the foregoing method embodiments.
[0348] FIG. 17 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 1700 shown in FIG. 17 includes a receiving unit 1710.
[0349] The receiving unit 1710 is configured to receive a first message sent by a first network element in a core network, the first message containing an address of the terminal device, the address of the terminal device being used for transmission of signaling between the terminal device and the core network.
[0350] In some embodiments, the terminal device further includes a processing unit configured to register with the core network; or perform network slice authentication and / or authorization successfully.
[0351] In some embodiments, the terminal device further includes a sending unit configured to send a fourth message to an access network device, the fourth message including an identity of the terminal device and the address of the terminal device.
[0352] In some embodiments, the fourth message is an AS message; or the fourth message is a NAS message.
[0353] In some embodiments, the first message further includes one or more of the following: the identity of the terminal device; an address and / or FQDN of a third network element in the core network, the third network element being used to discover other network elements in the core network; addresses and / or FQDNs of one or more fourth network elements in the core network, the fourth network elements being network elements in the core network used to serve the terminal device; security parameters used to establish a security context between the terminal device and the third network element; slice information.
[0354] In some embodiments, the third network element is a network repository function.
[0355] In some embodiments, the address of the terminal device and an address of an access network device belong to different address sets.
[0356] In some embodiments, the address of the terminal device is an IP address of the terminal device.
[0357] FIG. 18 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 1800 shown in FIG. 18 is a first network element in a core network, and the communication device 1800 includes a sending unit 1810.
[0358] The sending unit 1810 is configured to send a first message to a terminal device, the first message containing an address of the terminal device, the address of the terminal device being used for transmission of signaling between the terminal device and the core network.
[0359] In some embodiments, the sending unit is configured to send a second message to a second network element in the core network, the second message comprising an identifier of the terminal device and an address of the terminal device.
[0360] In some embodiments, the second network element comprises a unified data management function and / or a unified data repository.
[0361] In some embodiments, the sending unit is configured to send a third message to a server, the third message being used to request the server to allocate an address to the terminal device; and the receiving unit is configured to receive an address of the terminal device sent by the server.
[0362] In some embodiments, the third message comprises an identifier of the terminal device and / or slice information of the terminal device.
[0363] In some embodiments, the third message is sent after the terminal device successfully registers to the core network.
[0364] In some embodiments, the first message further comprises one or more of the following: an identifier of the terminal device; an address and / or FQDN of a third network element in the core network, the third network element being used to discover other network elements in the core network; an address and / or FQDN of one or more fourth network elements in the core network, the fourth network elements being network elements in the core network for serving the terminal device; a security parameter, used for the terminal device to establish a security context with a network element in the core network; slice information.
[0365] In some embodiments, the third network element is a network repository function.
[0366] In some embodiments, the address of the terminal device and an address of an access network device belong to different address sets.
[0367] In some embodiments, the address of the terminal device is an IP address of the terminal device.
[0368] FIG. 19 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 1900 shown in FIG. 19 is a second network element in a core network, and the communication device 1900 comprises a receiving unit 1910.
[0369] The receiving unit 1910 is configured to receive a second message, the second message comprising an identifier of a terminal device and an address of the terminal device, the address of the terminal device being used for transmission of signaling between the terminal device and the core network.
[0370] In some embodiments, the second network element is a unified data management function and / or a unified data repository.
[0371] FIG. 20 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 2000 shown in FIG. 20 includes a sending unit 2010.
[0372] The sending unit 2010 is configured to send a fifth message to a target network element, where the fifth message is used to indicate that the terminal device supports address-based signaling transmission.
[0373] In some embodiments, the terminal device further includes a first receiving unit configured to receive a sixth message sent by the target network element, where the sixth message is used to indicate one or more of the following: the target network element supports address-based signaling transmission; the target network element accepts address-based signaling transmission; the target network element does not support address-based signaling transmission; and the target network element rejects address-based signaling transmission.
[0374] In some embodiments, the target network element is an access network device.
[0375] In some embodiments, the terminal device further includes a second receiving unit configured to receive broadcast information sent by the target network element, where the broadcast information is used to indicate that the target network element supports address-based signaling transmission.
[0376] In some embodiments, the broadcast information is carried in a system information block.
[0377] In some embodiments, the target network element is a network element in the core network.
[0378] In some embodiments, the target network element is an authentication service function or a mobility management network element.
[0379] In some embodiments, the fifth message is a registration request message.
[0380] In some embodiments, the address is an IP address.
[0381] FIG. 21 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 2100 shown in FIG. 21 is a target network element, and the communication device 2100 includes a receiving unit 2110.
[0382] The receiving unit 2110 is configured to receive a fifth message sent by a terminal device, where the fifth message is used to indicate that the terminal device supports address-based signaling transmission.
[0383] In some embodiments, the communication device further comprises a first sending unit configured to send a sixth message to the terminal device, the sixth message being used to indicate one or more of the following: the target network element supports address-based signaling transmission; the target network element accepts address-based signaling transmission; the target network element does not support address-based signaling transmission; and the target network element rejects address-based signaling transmission.
[0384] In some embodiments, the target network element is an access network device.
[0385] In some embodiments, the communication device further comprises a second sending unit configured to send broadcast information to the terminal device, the broadcast information being used to indicate that the target network element supports address-based signaling transmission.
[0386] In some embodiments, the broadcast information is carried in a system information block.
[0387] In some embodiments, the target network element is a network element in a core network.
[0388] In some embodiments, the target network element is an authentication service function or a mobility management network element.
[0389] In some embodiments, the fifth message is a registration request message.
[0390] In some embodiments, the address is an IP address.
[0391] FIG. 22 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 2200 shown in FIG. 22 is an access network device, and the communication device 2200 comprises a receiving unit 2210.
[0392] The receiving unit 2210 is configured to receive a seventh message sent by a terminal device, the seventh message comprising one or more of the following: first NAS signaling, the first NAS signaling being NAS signaling sent by the terminal device to a fourth network element in a core network; an address of the terminal device; and an address of the fourth network element.
[0393] In some embodiments, the communication device further comprises, after receiving the seventh message, a first sending unit configured to send a first data packet to the fourth network element, the first data packet being a data packet transmitted based on the address, and the first data packet comprising the first NAS signaling.
[0394] In some embodiments, the seventh message comprises a first NAS container, and the first NAS signaling is carried in the first NAS container.
[0395] In some embodiments, the seventh message is an RRC message.
[0396] In some embodiments, the first data packet comprises one or more of: an address of the access network device; an address of the fourth network element; an address of the terminal device.
[0397] In some embodiments, the first data packet comprises a first packet header and / or a second packet header, a source address of the first packet header is an address of the access network device, a destination address of the first packet header is an address of the fourth network element, a source address of the second packet header is an address of the terminal device, and a destination address of the second packet header is an address of the fourth network element.
[0398] In some embodiments, the receiving unit is configured to receive a second data packet transmitted by the fourth network element, the second data packet being an address-based data packet, and the second data packet comprising a second NAS signaling, the second NAS signaling being a NAS signaling transmitted by the fourth network element in response to the first NAS signaling.
[0399] In some embodiments, the second data packet comprises one or more of: an address of the access network device; an address of the fourth network element; an address of the terminal device.
[0400] In some embodiments, the second data packet comprises a third packet header and / or a fourth packet header, a source address of the third packet header is an address of the fourth network element, a destination address of the third packet header is an address of the access network device, a source address of the fourth packet header is an address of the fourth network element, and a destination address of the fourth packet header is an address of the terminal device.
[0401] In some embodiments, the communication device further comprises a second sending unit configured to send an eighth message to the terminal device, the eighth message comprising the second NAS signaling.
[0402] In some embodiments, the eighth message further comprises an address of the terminal device and / or an address of the fourth network element.
[0403] In some embodiments, the eighth message comprises a second NAS container, and the second NAS signaling is carried in the second NAS container.
[0404] In some embodiments, the eighth message is an RRC message.
[0405] In some embodiments, the receiving unit is configured to receive a ninth message sent by the terminal device, the ninth message comprising first information used to request an address of the fourth network element from a third network element of the core network; and a third sending unit is configured to send a third data packet to the third network element, the third data packet being an address-based data packet, and the third data packet comprising the first information.
[0406] In some embodiments, the first information comprises one or more of the following: an identifier of the terminal device; a type of the fourth network element; an FQDN of the fourth network element; and slice information.
[0407] In some embodiments, the ninth message comprises a third NAS container, and the first information is carried in the third NAS container.
[0408] In some embodiments, the ninth message further comprises an address of the terminal device and / or an address of the third network element.
[0409] In some embodiments, the ninth message is an RRC message.
[0410] In some embodiments, the third data packet further comprises one or more of the following: an address of the access network device; an address of the third network element; and an address of the terminal device.
[0411] In some embodiments, the third data packet comprises a fifth packet header and / or a sixth packet header, the source address of the fifth packet header is an address of the access network device, the destination address of the fifth packet header is an address of the third network element, the source address of the sixth packet header is an address of the terminal device, and the destination address of the sixth packet header is an address of the third network element.
[0412] In some embodiments, the receiving unit is configured to receive a fourth data packet sent by the third network element, the fourth data packet being an address-based data packet, and the fourth data packet comprising one or more of the following: an address of the fourth network element; an FQDN of the fourth network element; a type of the fourth network element; an identifier of the terminal device; an address of the terminal device; an address of the access network device; and slice information.
[0413] In some embodiments, the fourth data packet comprises a seventh packet header and / or an eighth packet header, the source address of the seventh packet header is an address of the third network element, the destination address of the seventh packet header is an address of the access network device, the source address of the eighth packet header is an address of the third network element, and the destination address of the eighth packet header is an address of the terminal device.
[0414] In some embodiments, the communication device further comprises a fourth sending unit configured to send second information to a fifth network element of the core network, the second information being used to request an identifier of the terminal device, and the second information comprising an address of the terminal device; and the receiving unit is configured to receive the identifier of the terminal device sent by the fifth network element.
[0415] In some embodiments, the communication device further comprises a fifth sending unit configured to send a tenth message to the terminal device, the tenth message comprising one or more of the following: an address of the fourth network element; a FQDN of the fourth network element; a type of the fourth network element; an identifier of the terminal device; and an address of the terminal device.
[0416] In some embodiments, the tenth message comprises a fourth NAS container, and the address of the fourth network element is carried in the fourth NAS container.
[0417] In some embodiments, the tenth message is an RRC message.
[0418] In some embodiments, the first data packet is an IP data packet.
[0419] FIG. 23 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 2300 shown in FIG. 23 comprises a sending unit 2310.
[0420] The sending unit 2310 is configured to send a seventh message to an access network device, the seventh message comprising one or more of the following: first NAS signaling, the first NAS signaling being NAS signaling sent by the terminal device to a fourth network element in a core network; an address of the terminal device; and an address of the fourth network element.
[0421] In some embodiments, the seventh message comprises a first NAS container, and the first NAS signaling is carried in the first NAS container.
[0422] In some embodiments, the seventh message is an RRC message.
[0423] In some embodiments, the terminal device further comprises a first receiving unit configured to receive an eighth message sent by the access network device, the eighth message comprising second NAS signaling, the second NAS signaling being NAS signaling sent by the fourth network element in response to the first NAS signaling.
[0424] In some embodiments, the eighth message further comprises the address of the terminal device and / or the address of the fourth network element.
[0425] In some embodiments, the eighth message contains a second NAS container, and the second NAS signaling is carried in the second NAS container.
[0426] In some embodiments, the eighth message is an RRC message.
[0427] In some embodiments, the sending unit is configured to send, to the access network device, a ninth message containing first information, the first information being used to request an address of the fourth network element from a third network element of the core network.
[0428] In some embodiments, the first information contains one or more of the following: an identifier of the terminal device; a type of the fourth network element; an FQDN of the fourth network element; slice information.
[0429] In some embodiments, the ninth message contains a third NAS container, and the first information is carried in the third NAS container.
[0430] In some embodiments, the ninth message further includes an address of the terminal device and / or an address of the third network element.
[0431] In some embodiments, the ninth message is an RRC message.
[0432] In some embodiments, the terminal device further includes a second receiving unit configured to receive a tenth message sent by the access network device, the tenth message containing one or more of the following: the address of the fourth network element; the FQDN of the fourth network element; the type of the fourth network element; the identifier of the terminal device; the address of the terminal device.
[0433] In some embodiments, the tenth message contains a fourth NAS container, and the address of the fourth network element is carried in the fourth NAS container.
[0434] In some embodiments, the tenth message is an RRC message.
[0435] In some embodiments, the address of the terminal device is an IP address.
[0436] FIG. 24 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 2400 shown in FIG. 24 is a fourth network element in a core network, and the communication device 2400 includes a receiving unit 2410.
[0437] The receiving unit 2410 is configured to receive a first data packet sent by an access network device, the first data packet being a data packet transmitted based on an address, and the first data packet containing first NAS signaling sent by a terminal device to the fourth network element.
[0438] In some embodiments, the first data packet comprises one or more of: an address of the access network device; an address of the fourth network element; an address of the terminal device.
[0439] In some embodiments, the first data packet comprises a first packet header and / or a second packet header, a source address of the first packet header is an address of the access network device, a destination address of the first packet header is an address of the fourth network element, a source address of the second packet header is an address of the terminal device, and a destination address of the second packet header is an address of the fourth network element.
[0440] In some embodiments, the communication device further comprises a sending unit configured to send a second data packet to the access network device, the second data packet is a data packet based on address transmission, and the second data packet comprises a second NAS signaling, the second NAS signaling is a NAS signaling sent by the fourth network element in response to the first NAS signaling.
[0441] In some embodiments, the second data packet comprises one or more of: an address of the access network device; an address of the fourth network element; an address of the terminal device.
[0442] In some embodiments, the second data packet comprises a third packet header and / or a fourth packet header, a source address of the third packet header is an address of the fourth network element, a destination address of the third packet header is an address of the access network device, a source address of the fourth packet header is an address of the fourth network element, and a destination address of the fourth packet header is an address of the terminal device.
[0443] In some embodiments, the first data packet is an IP data packet.
[0444] FIG. 25 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 2500 shown in FIG. 25 is a third network element in a core network, and the communication device 2500 comprises a receiving unit 2510.
[0445] The receiving unit is configured to receive a third data packet sent by an access network device, the third data packet is a data packet based on address transmission, and the third data packet comprises first information, the first information is used to request an address of a fourth network element in the core network from the third network element.
[0446] In some embodiments, the first information comprises one or more of: an identifier of the terminal device; a type of the fourth network element; an FQDN of the fourth network element; and slice information.
[0447] In some embodiments, the third data packet further comprises one or more of: an address of the access network device; an address of the third network element; an address of the terminal device.
[0448] In some embodiments, the third data packet comprises a fifth packet header and / or a sixth packet header, a source address of the fifth packet header is an address of the access network device, a destination address of the fifth packet header is an address of the third network element, a source address of the sixth packet header is an address of the terminal device, and a destination address of the sixth packet header is an address of the third network element.
[0449] In some embodiments, the communication device further comprises a sending unit configured to send a fourth data packet to the access network device, the fourth data packet being an address-based transmission data packet, and the fourth data packet comprising one or more of: an address of the fourth network element; a FQDN of the fourth network element; an identifier of the terminal device; an address of the terminal device; an address of the access network device; and slice information.
[0450] In some embodiments, the fourth data packet comprises a seventh packet header and / or an eighth packet header, a source address of the seventh packet header is an address of the third network element, a destination address of the seventh packet header is an address of the access network device, a source address of the eighth packet header is an address of the third network element, and a destination address of the eighth packet header is an address of the terminal device.
[0451] In some embodiments, the third data packet is an IP data packet.
[0452] FIG. 26 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 2600 shown in FIG. 26 is an access network device, and the communication device 2600 comprises a receiving unit 2610.
[0453] The receiving unit 2610 is configured to receive a fifth data packet sent by a fourth network element in a core network, the fifth data packet being an address-based transmission data packet, and the fifth data packet comprising a third NAS signaling, the third NAS signaling being a NAS signaling sent by the fourth network element to a terminal device.
[0454] In some embodiments, the fifth data packet further comprises one or more of: an address of the fourth network element; an address of the terminal device; an address of the access network device; and slice information.
[0455] In some embodiments, the fifth data packet comprises a ninth packet header and / or a tenth packet header, the source address of the ninth packet header is the address of the fourth network element, the destination address of the ninth packet header is the address of the access network device, the source address of the tenth packet header is the address of the fourth network element, and the destination address of the tenth packet header is the address of the terminal device.
[0456] In some embodiments, the communication device further comprises a sending unit configured to send an eleventh message to the terminal device, the eleventh message comprising one or more of the following: the third NAS signaling; the address of the fourth network element; and the address of the terminal device.
[0457] In some embodiments, the eleventh message comprises a fifth NAS container, and the third NAS signaling is carried in the fifth NAS container.
[0458] In some embodiments, the eleventh message is an RRC message.
[0459] In some embodiments, if the terminal device is in an idle state, the sending unit is configured to send a paging message to the terminal device, the paging message comprising the identity of the terminal device.
[0460] In some embodiments, the fifth data packet is an IP data packet.
[0461] FIG. 27 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 2700 shown in FIG. 27 is a fourth network element in a core network, and the communication device 2700 comprises a sending unit 2710.
[0462] The sending unit 2710 is configured to send a fifth data packet to an access network device, the fifth data packet being a data packet transmitted based on an address, and the fifth data packet comprising third NAS signaling, the third NAS signaling being NAS signaling sent by the fourth network element to a terminal device.
[0463] In some embodiments, the fifth data packet further comprises one or more of the following: the address of the fourth network element; the address of the terminal device; the address of the access network device; and slice information.
[0464] In some embodiments, the fifth data packet comprises a ninth packet header and / or a tenth packet header, the source address of the ninth packet header is the address of the fourth network element, the destination address of the ninth packet header is the address of the access network device, the source address of the tenth packet header is the address of the fourth network element, and the destination address of the tenth packet header is the address of the terminal device.
[0465] In some embodiments, the sending unit is configured to send a twelfth message to a second network element of the core network, the twelfth message being used to request an address of the terminal device and / or an address of the access network device.
[0466] In some embodiments, the twelfth message is used to request the address of the terminal device or the address of the access network device, and the twelfth message comprises an identifier of the terminal device; or the twelfth message is used to request the address of the access network device, and the twelfth message comprises the identifier of the terminal device and / or the address of the terminal device.
[0467] In some embodiments, the communication device further comprises a receiving unit configured to receive a thirteenth message sent by the second network element, the thirteenth message comprising one or more of the following: the address of the access network device; the identifier of the access network device; the identifier of the terminal device.
[0468] In some embodiments, the second network element comprises a unified data management function and / or a unified data repository.
[0469] In some embodiments, the fifth data packet is an IP data packet.
[0470] FIG. 28 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 2800 shown in FIG. 28 is a second network element in a core network, and the communication device 2800 comprises a receiving unit 2810.
[0471] The receiving unit 2810 is configured to receive a twelfth message sent by a fourth network element, the twelfth message being used to request an address of a terminal device and / or an address of an access network device serving the terminal device; wherein the address of the terminal device is used for transmission of signaling between the terminal device and the core network.
[0472] In some embodiments, the twelfth message is used to request the address of the terminal device or the address of the access network device, and the twelfth message comprises an identifier of the terminal device; or the twelfth message is used to request the address of the access network device, and the twelfth message comprises the identifier of the terminal device and / or the address of the terminal device.
[0473] In some embodiments, the communication device further comprises a sending unit configured to send a thirteenth message to the fourth network element, the thirteenth message comprising one or more of the following: the address of the access network device; the identifier of the access network device; the identifier of the terminal device.
[0474] In some embodiments, the second network element comprises a unified data management function and / or a unified data repository.
[0475] In some embodiments, the address of the access network device is an IP address.
[0476] FIG. 29 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 2900 shown in FIG. 29 includes a receiving unit 2910.
[0477] The receiving unit 2910 is configured to receive an eleventh message sent by an access network device, the eleventh message including one or more of the following: third NAS signaling, the third NAS signaling being NAS signaling sent by a fourth network element in a core network to the terminal device; an address of the fourth network element; an address of the terminal device.
[0478] In some embodiments, the eleventh message includes a fifth NAS container, and the third NAS signaling is carried in the fifth NAS container.
[0479] In some embodiments, the eleventh message is an RRC message.
[0480] In some embodiments, the receiving unit is configured to receive a paging message sent by the access network device, the paging message including an identifier of the terminal device.
[0481] In some embodiments, the address of the terminal device is an IP address.
[0482] FIG. 30 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. The dashed line in FIG. 30 indicates that the unit or module is optional. The apparatus 3000 can be used to implement the methods described in the foregoing method embodiments. The apparatus 3000 can be a chip, a terminal device, or a network device.
[0483] The apparatus 3000 can include one or more processors 3010. The processor 3010 can support the apparatus 3000 to implement the methods described in the foregoing method embodiments. The processor 3010 can be a general purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.
[0484] The apparatus 3000 can further include one or more memories 3020. The memories 3020 store programs, which can be executed by the processor 3010, so that the processor 3010 performs the methods described in the foregoing method embodiments. The memories 3020 can be independent of the processor 3010 or integrated in the processor 3010.
[0485] The apparatus 3000 can further include a transceiver 3030. The processor 3010 can communicate with other devices or chips through the transceiver 3030. For example, the processor 3010 can perform data transceiving with other devices or chips through the transceiver 3030.
[0486] The embodiments of the present application further provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the embodiments of the present application.
[0487] The embodiments of the present application further provide a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the embodiments of the present application.
[0488] The embodiments of the present application further provide a computer program. The computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the method performed by the terminal or network device in the embodiments of the present application.
[0489] It should be understood that the terms "system" and "network" can be used interchangeably in the present application. In addition, the terms used in the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the present application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.
[0490] In the embodiments of the present application, the "indication" mentioned can be direct indication, or indirect indication, or can be an indication that has an associated relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; or it can mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or it can mean that A and B have an associated relationship.
[0491] In embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.
[0492] In embodiments of the present application, the term "corresponding" can mean a direct or indirect corresponding relationship between the two, can also mean an associated relationship between the two, or can indicate a relationship with the indicated, configured, and the like.
[0493] In embodiments of the present application, "predefined" or "preconfigured" can be implemented by pre-saving corresponding codes, tables or other ways that can be used to indicate related information in devices (for example, including terminal devices and network devices), and the present application does not limit the specific implementation manner. For example, predefinition can refer to definition in a protocol.
[0494] In embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, which can include, for example, an LTE protocol, an NR protocol, and a related protocol applied to a future communication system, and the present application does not limit this.
[0495] In embodiments of the present application, the term "and / or" is only a description of the association relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents an "or" relationship between the associated objects before and after it.
[0496] In various embodiments of the present application, the size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0497] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other means. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can be in another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the shown or discussed mutual ones can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.
[0498] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed on multiple network units. Part or all of the units can be selected to achieve the purpose of the embodiment of the present application according to actual needs.
[0499] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit.
[0500] In the above embodiments, all or part can be realized by software, hardware, firmware or any combination thereof. When realized by software, all or part can be realized in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, the computer program instructions produce the processes or functions described in the embodiments of the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium readable by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (such as floppy disk, hard disk, magnetic tape), optical media (such as digital video disc (DVD)) or semiconductor media (such as solid state disk (SSD)) and the like.
[0501] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, any skilled person in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. A communication method characterized by comprising: The method comprises: The terminal device receives a first message sent by a first network element in a core network, the first message containing an address of the terminal device, the address of the terminal device being used for signaling transmission between the terminal device and the core network.
2. The method of claim 1, wherein, Before the terminal device receives the first message sent by the first network element in the core network, the method further comprises: The terminal device registers to the core network; or The terminal device performs network slice authentication and / or authorization successfully.
3. The method according to claim 1 or 2, characterized in that, The method further comprises: The terminal device sends a fourth message to an access network device, the fourth message comprising an identifier of the terminal device and the address of the terminal device.
4. The method of claim 3, wherein, The fourth message is an AS message; or the fourth message is an NAS message.
5. The method according to any one of claims 1 to 4, characterized in that, The first message further comprises one or more of the following: The identifier of the terminal device; An address and / or FQDN of a third network element in the core network, the third network element being used for discovering other network elements in the core network; An address and / or FQDN of one or more fourth network elements in the core network, the fourth network elements being network elements in the core network for serving the terminal device; Security parameters for establishing a security context between the terminal device and the third network element; Slice information.
6. The method of claim 5, wherein, The third network element is a network repository function.
7. The method according to any one of claims 1 to 6, characterized in that, The address of the terminal device and an address of the access network device belong to different address sets.
8. The method according to any one of claims 1 to 7, characterized in that, The address of the terminal device is an IP address of the terminal device.
9. A communication method characterized by comprising: The method comprises: A first network element in a core network sends a first message to a terminal device, the first message containing an address of the terminal device, the address of the terminal device being used for signaling transmission between the terminal device and the core network.
10. The method of claim 9, wherein, The method further comprises: The first network element sends a second message to a second network element in the core network, the second message comprising an identifier of the terminal device and the address of the terminal device.
11. The method of claim 10, wherein, The second network element comprises a unified data management function and / or a unified data repository.
12. The method according to any one of claims 9 to 11, characterized in that, Before the first network element in the core network sends the first message to the terminal device, the method further comprises: The first network element sends a third message to a server, the third message being used for requesting the server to allocate an address for the terminal device; The first network element receives the address of the terminal device sent by the server.
13. The method of claim 12, wherein, The third message contains an identifier of the terminal device and / or slice information of the terminal device.
14. The method according to claim 12 or 13, characterized in that, The third message is sent after the terminal device successfully registers to the core network.
15. The method according to any one of claims 9 to 14, characterized in that, The first message further comprises one or more of the following: The identifier of the terminal device; An address and / or FQDN of a third network element in the core network, the third network element being used for discovering other network elements in the core network; An address and / or FQDN of one or more fourth network elements in the core network, the fourth network elements being network elements in the core network for serving the terminal device; Security parameters for establishing a security context between the terminal device and a network element in the core network; Slice information.
16. The method of claim 15, wherein, The third network element is a network repository function.
17. The method according to any one of claims 9 to 16, characterized in that, The address of the terminal device and an address of the access network device belong to different address sets.
18. The method according to any one of claims 9 to 17, characterized in that, The address of the terminal device is an IP address of the terminal device.
19. A method of communication, comprising: Comprising: The second network element in the core network receives a second message, the second message comprising an identity of a terminal device and an address of the terminal device, the address of the terminal device being used for transmission of signaling by the terminal device with the core network.
20. The method of claim 19, wherein, The second network element is a unified data management function and / or a unified data repository.
21. A method of communication, comprising: Comprising: The terminal device sends a fifth message to a target network element, the fifth message being used to indicate that the terminal device supports address-based transmission of signaling.
22. The method of claim 21, wherein, The method further comprises: The terminal device receives a sixth message sent by the target network element, the sixth message being used to indicate one or more of: The target network element supports address-based transmission of signaling; The target network element accepts address-based transmission of signaling; The target network element does not support address-based transmission of signaling; The target network element rejects address-based transmission of signaling.
23. The method of claim 21 or 22, wherein, The target network element is an access network device.
24. The method of claim 23, wherein, Before the terminal device sends a fifth message to a target network element, the method further comprises: The terminal device receives broadcast information sent by the target network element, the broadcast information being used to indicate that the target network element supports address-based transmission of signaling.
25. The method of claim 24, wherein, The broadcast information is carried in a system information block.
26. The method of claim 21 or 22, wherein, The target network element is a network element in the core network.
27. The method of claim 26, wherein, The target network element is an authentication server function or a mobility management network element.
28. The method of any one of claims 21-27, wherein, The fifth message is a registration request message.
29. The method of any one of claims 21-28, wherein, The address is an IP address.
30. A method of communication, comprising: Comprising: A target network element receives a fifth message sent by a terminal device, the fifth message being used to indicate that the terminal device supports address-based transmission of signaling.
31. The method of claim 30, wherein, The method further comprises: The target network element sends a sixth message to the terminal device, the sixth message being used to indicate one or more of: The target network element supports address-based transmission of signaling; The target network element accepts address-based transmission of signaling; The target network element does not support address-based transmission of signaling; The target network element rejects address-based transmission of signaling.
32. The method of claim 30 or 31, wherein, The target network element is an access network device.
33. The method of claim 32, wherein, Before the target network element receives a fifth message sent by a terminal device, the method further comprises: The target network element sends broadcast information to the terminal device, the broadcast information being used to indicate that the target network element supports address-based transmission of signaling.
34. The method of claim 33, wherein, The broadcast information is carried in a system information block.
35. The method of claim 30 or 31, wherein, The target network element is a network element in the core network.
36. The method of claim 35, wherein, The target network element is an authentication server function or a mobility management network element.
37. The method of any one of claims 30-36, wherein, The fifth message is a registration request message.
38. The method of any one of claims 30-37, wherein, The address is an IP address.
39. A method of communication, comprising: Comprising: An access network device receives a seventh message sent by a terminal device, the seventh message comprising one or more of: First NAS signaling, the first NAS signaling being NAS signaling sent by the terminal device to a fourth network element in a core network; An address of the terminal device; An address of the fourth network element.
40. The method of claim 39, wherein, The method further comprises: After receiving the seventh message, the access network device sends a first data packet to the fourth network element, the first data packet is an address-based data packet, and the first data packet contains the first NAS signaling.
41. The method of claim 39 or 40, wherein, The seventh message contains a first NAS container, and the first NAS signaling is carried in the first NAS container.
42. The method of any one of claims 39-41, wherein, The seventh message is an RRC message.
43. The method of any one of claims 39-42, wherein, The first data packet includes one or more of the following: An address of the access network device; An address of the fourth network element; An address of the terminal device.
44. The method of claim 43, wherein, The first data packet includes a first packet header and / or a second packet header, a source address of the first packet header is an address of the access network device, a destination address of the first packet header is an address of the fourth network element, a source address of the second packet header is an address of the terminal device, and a destination address of the second packet header is an address of the fourth network element.
45. The method of any one of claims 39-44, wherein, The method further includes: The access network device receives a second data packet sent by the fourth network element, the second data packet is an address-based data packet, and the second data packet contains second NAS signaling, the second NAS signaling is NAS signaling sent by the fourth network element in response to the first NAS signaling.
46. The method of claim 45, wherein, The second data packet includes one or more of the following: an address of the access network device, an address of the fourth network element, and an address of the terminal device.
47. The method of claim 46, wherein, The second data packet includes a third packet header and / or a fourth packet header, a source address of the third packet header is an address of the fourth network element, a destination address of the third packet header is an address of the access network device, a source address of the fourth packet header is an address of the fourth network element, and a destination address of the fourth packet header is an address of the terminal device.
48. The method of any one of claims 45-47, wherein, The method further includes: The access network device sends an eighth message to the terminal device, and the eighth message contains the second NAS signaling.
49. The method of claim 48, wherein, The eighth message further includes an address of the terminal device and / or an address of the fourth network element.
50. The method of claim 48 or 49, wherein, The eighth message contains a second NAS container, and the second NAS signaling is carried in the second NAS container.
51. The method of any one of claims 48-50, wherein, The eighth message is an RRC message.
52. The method of any one of claims 39-51, wherein, Before the access network device receives a seventh message sent by a terminal device, the method further includes: The access network device receives a ninth message sent by the terminal device, and the ninth message contains first information, the first information being used to request an address of the fourth network element from a third network element of the core network; The access network device sends a third data packet to the third network element, the third data packet being an address-based data packet, and the third data packet contains the first information.
53. The method of claim 52, wherein, The first information includes one or more of the following: An identifier of the terminal device; A type of the fourth network element; An FQDN of the fourth network element; Slice information.
54. The method of claim 53, wherein, The ninth message contains a third NAS container, and the first information is carried in the third NAS container.
55. The method of any one of claims 52-54, wherein, The ninth message further includes an address of the terminal device and / or an address of the third network element.
56. The method of any one of claims 52-55, wherein, The ninth message is an RRC message.
57. The method of any one of claims 52-56, wherein, The third data packet further includes one or more of the following: an address of the access network device; an address of the third network element; an address of the terminal device.
58. The method of claim 57, wherein, The third data packet comprises a fifth packet header and / or a sixth packet header, a source address of the fifth packet header is an address of the access network device, a destination address of the fifth packet header is an address of the third network element, a source address of the sixth packet header is an address of the terminal device, and a destination address of the sixth packet header is an address of the third network element.
59. The method of any one of claims 52-58, wherein, The method further comprises: The access network device receives a fourth data packet sent by the third network element, the fourth data packet is a data packet based on address transmission, and the fourth data packet comprises one or more of the following: an address of the fourth network element; an FQDN of the fourth network element; a type of the fourth network element; an identifier of the terminal device; an address of the terminal device; an address of the access network device; slice information.
60. The method of claim 59, wherein, The fourth data packet comprises a seventh packet header and / or an eighth packet header, a source address of the seventh packet header is an address of the third network element, a destination address of the seventh packet header is an address of the access network device, a source address of the eighth packet header is an address of the third network element, and a destination address of the eighth packet header is an address of the terminal device.
61. The method of claim 59 or 60, wherein, The method further comprises: The access network device sends second information to a fifth network element of the core network, the second information is used for requesting an identifier of the terminal device, and the second information comprises an address of the terminal device; The access network device receives an identifier of the terminal device sent by the fifth network element.
62. The method of any one of claims 52-61, wherein, The method further comprises: The access network device sends a tenth message to the terminal device, the tenth message comprises one or more of the following: an address of the fourth network element; an FQDN of the fourth network element; a type of the fourth network element; an identifier of the terminal device; an address of the terminal device.
63. The method of claim 62, wherein, The tenth message comprises a fourth NAS container, and the address of the fourth network element is carried in the fourth NAS container.
64. The method of claim 62 or 63, wherein, The tenth message is an RRC message.
65. The method of any one of claims 39-64, wherein, The first data packet is an IP data packet.
66. A method of communication, the method comprising: Comprise: The terminal device sends a seventh message to the access network device, the seventh message comprises one or more of the following: first NAS signaling, the first NAS signaling is NAS signaling sent by the terminal device to a fourth network element in the core network; an address of the terminal device; an address of the fourth network element.
67. The method of claim 66, wherein, The seventh message comprises a first NAS container, and the first NAS signaling is carried in the first NAS container.
68. The method of claim 66 or 67, wherein, The seventh message is an RRC message.
69. The method of any one of claims 66-68, wherein, The method further comprises: The terminal device receives an eighth message sent by the access network device, the eighth message comprises second NAS signaling, and the second NAS signaling is NAS signaling sent by the fourth network element in response to the first NAS signaling.
70. The method of claim 69, wherein, The eighth message further comprises an address of the terminal device and / or an address of the fourth network element.
71. The method of claim 69 or 70, wherein, The eighth message comprises a second NAS container, and the second NAS signaling is carried in the second NAS container.
72. The method of any one of claims 69-71, wherein, The eighth message is an RRC message.
73. The method of any one of claims 66-72, wherein, Before the terminal device sends the seventh message to the access network device, the method further comprises: The terminal device sends a ninth message to the access network device, and the ninth message comprises first information, and the first information is used to request the address of the fourth network element from a third network element of the core network.
74. The method of claim 73, wherein, The first information comprises one or more of the following: An identifier of the terminal device; A type of the fourth network element; An FQDN of the fourth network element; Slice information.
75. The method of claim 74, wherein, The ninth message comprises a third NAS container, and the first information is carried in the third NAS container.
76. The method of any one of claims 73-75, wherein, The ninth message further comprises an address of the terminal device and / or an address of the third network element.
77. The method of any one of claims 73-76, wherein, The ninth message is an RRC message.
78. The method of any one of claims 73-77, wherein, The method further comprises: The terminal device receives a tenth message sent by the access network device, and the tenth message comprises one or more of the following: An address of the fourth network element; An FQDN of the fourth network element; A type of the fourth network element; An identifier of the terminal device; An address of the terminal device.
79. The method of claim 78, wherein, The tenth message comprises a fourth NAS container, and the address of the fourth network element is carried in the fourth NAS container.
80. The method of claim 78 or 79, wherein, The tenth message is an RRC message.
81. The method of any one of claims 66-80, wherein, The address of the terminal device is an IP address.
82. A method of communication, the method comprising: Comprise: A fourth network element in a core network receives a first data packet sent by an access network device, the first data packet is a data packet based on address transmission, and the first data packet comprises first NAS signaling sent by a terminal device to the fourth network element.
83. The method of claim 82, wherein, The first data packet comprises one or more of the following: An address of the access network device; An address of the fourth network element; An address of the terminal device.
84. The method of claim 83, wherein, The first data packet comprises a first packet header and / or a second packet header, a source address of the first packet header is an address of the access network device, a destination address of the first packet header is an address of the fourth network element, a source address of the second packet header is an address of the terminal device, and a destination address of the second packet header is an address of the fourth network element.
85. The method of any one of claims 82-84, wherein, The method further comprises: The fourth network element sends a second data packet to the access network device, the second data packet is a data packet based on address transmission, and the second data packet comprises second NAS signaling, and the second NAS signaling is NAS signaling sent by the fourth network element in response to the first NAS signaling.
86. The method of claim 85, wherein, The second data packet comprises one or more of the following: An address of the access network device; An address of the fourth network element; An address of the terminal device.
87. The method of claim 86, wherein, The second data packet comprises a third packet header and / or a fourth packet header, a source address of the third packet header is an address of the fourth network element, a destination address of the third packet header is an address of the access network device, a source address of the fourth packet header is an address of the fourth network element, and a destination address of the fourth packet header is an address of the terminal device.
88. The method of any one of claims 82-87, wherein, The first data packet is an IP data packet.
89. A method of communication, the method comprising: Comprise: A third network element of the core network receives a third data packet sent by the access network device, the third data packet is a data packet based on address transmission, and the third data packet contains first information used for requesting an address of a fourth network element in the core network from the third network element.
90. The method of claim 89, wherein, The first information contains one or more of the following: An identifier of the terminal device; A type of the fourth network element; An FQDN of the fourth network element; Slice information.
91. The method of claim 89 or 90, wherein, The third data packet further includes one or more of the following: An address of the access network device; An address of the third network element; An address of the terminal device.
92. The method of claim 91, wherein, The third data packet includes a fifth packet header and / or a sixth packet header, a source address of the fifth packet header is an address of the access network device, a destination address of the fifth packet header is an address of the third network element, a source address of the sixth packet header is an address of the terminal device, and a destination address of the sixth packet header is an address of the third network element.
93. The method of any one of claims 89-92, wherein, The method further includes: The third network element sends a fourth data packet to the access network device, the fourth data packet is a data packet based on address transmission, and the fourth data packet contains one or more of the following: An address of the fourth network element; An FQDN of the fourth network element; An identifier of the terminal device; An address of the terminal device; An address of the access network device; Slice information.
94. The method of claim 93, wherein, The fourth data packet includes a seventh packet header and / or an eighth packet header, a source address of the seventh packet header is an address of the third network element, a destination address of the seventh packet header is an address of the access network device, a source address of the eighth packet header is an address of the third network element, and a destination address of the eighth packet header is an address of the terminal device.
95. The method of any one of claims 89-94, wherein, The third data packet is an IP data packet.
96. A method of communication, comprising: The method includes: An access network device receives a fifth data packet sent by a fourth network element in a core network, the fifth data packet is a data packet based on address transmission, and the fifth data packet contains third NAS signaling, which is NAS signaling sent by the fourth network element to a terminal device.
97. The method of claim 96, wherein, The fifth data packet further includes one or more of the following: An address of the fourth network element; An address of the terminal device; An address of the access network device; Slice information.
98. The method of claim 97, wherein, The fifth data packet includes a ninth packet header and / or a tenth packet header, a source address of the ninth packet header is an address of the fourth network element, a destination address of the ninth packet header is an address of the access network device, a source address of the tenth packet header is an address of the fourth network element, and a destination address of the tenth packet header is an address of the terminal device.
99. The method of any one of claims 96-98, wherein, The method further includes: The access network device sends an eleventh message to the terminal device, and the eleventh message contains one or more of the following: The third NAS signaling; An address of the fourth network element; An address of the terminal device.
100. The method of claim 99, wherein, The eleventh message contains a fifth NAS container, and the third NAS signaling is carried in the fifth NAS container.
101. The method of claim 99 or 100, wherein, The eleventh message is an RRC message.
102. The method of any one of claims 99-101, wherein, Before the access network device sends the eleventh message to the terminal device, the method further includes: If the terminal device is in an idle state, the access network device sends a paging message to the terminal device, and the paging message contains an identity of the terminal device.
103. The method of any one of claims 96-102, wherein, The fifth data packet is an IP data packet.
104. A method of communication, comprising: Comprise: A fourth network element in the core network sends a fifth data packet to an access network device, the fifth data packet is a data packet transmitted based on an address, and the fifth data packet contains third NAS signaling, the third NAS signaling is NAS signaling sent by the fourth network element to a terminal device.
105. The method of claim 104, wherein, The fifth data packet further comprises one or more of: An address of the fourth network element; An address of the terminal device; An address of the access network device; Slice information.
106. The method of claim 105, wherein, The fifth data packet comprises a ninth packet header and / or a tenth packet header, a source address of the ninth packet header is an address of the fourth network element, a destination address of the ninth packet header is an address of the access network device, a source address of the tenth packet header is an address of the fourth network element, and a destination address of the tenth packet header is an address of the terminal device.
107. The method of any one of claims 104-106, wherein, Before the fourth network in the core network sends a fifth data packet to an access network device, the method further comprises: The fourth network element sends a twelfth message to a second network element of the core network, and the twelfth message is used to request an address of the terminal device and / or an address of the access network device.
108. The method of claim 107, wherein: The twelfth message is used to request the address of the terminal device or the address of the access network device, and the twelfth message contains an identity of the terminal device; or The twelfth message is used to request the address of the access network device, and the twelfth message contains an identity of the terminal device and / or an address of the terminal device.
109. The method of claim 107 or 108, wherein, The method further comprises: The fourth network element receives a thirteenth message sent by the second network element, and the thirteenth message contains one or more of: An address of the access network device; An identity of the access network device; An identity of the terminal device.
110. The method of any one of claims 107-109, wherein, The second network element comprises a unified data management function and / or a unified data repository.
111. The method of any one of claims 104-110, wherein, The fifth data packet is an IP data packet.
112. A method of communication, comprising: Comprise: A second network element in the core network receives a twelfth message sent by a fourth network element, and the twelfth message is used to request an address of a terminal device and / or an address of an access network device serving the terminal device; Wherein, the address of the terminal device is used for transmission of signaling between the terminal device and the core network.
113. The method of claim 112, wherein: The twelfth message is used to request the address of the terminal device or the address of the access network device, and the twelfth message contains an identity of the terminal device; or The twelfth message is used to request the address of the access network device, and the twelfth message contains an identity of the terminal device and / or an address of the terminal device.
114. The method of claim 112 or 113, wherein, The method further comprises: The second network element sends a thirteenth message to the fourth network element, and the thirteenth message contains one or more of: An address of the access network device; An identity of the access network device; An identity of the terminal device.
115. The method of any one of claims 112-114, wherein, The second network element comprises a unified data management function and / or a unified data repository.
116. The method of any one of claims 112-115, wherein, The address of the access network device is an IP address.
117. A method of communication, comprising: Comprise: The terminal device receives an eleventh message sent by the access network device, and the eleventh message comprises one or more of the following: Third NAS signaling, the third NAS signaling being NAS signaling sent by a fourth network element in the core network to the terminal device; The address of the fourth network element; The address of the terminal device.
118. The method of claim 117, wherein, The fifth NAS container contained in the eleventh message, and the third NAS signaling is carried in the fifth NAS container.
119. The method of claim 117 or 118, wherein, The eleventh message is an RRC message.
120. The method of any one of claims 117-119, wherein, Before the terminal device receives the eleventh message sent by the access network device, the method further comprises: The terminal device receives a paging message sent by the access network device, and the paging message comprises the identifier of the terminal device.
121. The method of any one of claims 117-120, wherein, The address of the terminal device is an IP address.
122. A terminal device, comprising: Comprise: A receiving unit, configured to receive a first message sent by a first network element in a core network, the first message comprising an address of the terminal device, The address of the terminal device is used for transmission of signaling between the terminal device and the core network.
123. The terminal device of claim 122, wherein, The terminal device further comprises a processing unit, configured to: Register with the core network; or Perform network slice identity authentication and / or authentication successfully.
124. The terminal device of claim 122 or 123, wherein, The terminal device further comprises: A sending unit, configured to send a fourth message to an access network device, the fourth message comprising an identifier of the terminal device and an address of the terminal device.
125. The terminal device of claim 124, wherein, The fourth message is an AS message; or the fourth message is a NAS message.
126. The terminal device of any one of claims 122 to 125, wherein, The first message further comprises one or more of the following: The identifier of the terminal device; The address and / or FQDN of a third network element in the core network, the third network element being used to discover other network elements in the core network; The address and / or FQDN of one or more fourth network elements in the core network, the fourth network element being a network element in the core network used to serve the terminal device; Security parameters for the terminal device to establish a security context with the third network element; Slice information.
127. The terminal device of claim 126, wherein, The third network element is a network repository function.
128. The terminal device of any one of claims 122 to 127, wherein, The address of the terminal device and the address of the access network device belong to different address sets.
129. The terminal device of any one of claims 122 to 128, wherein, The address of the terminal device is an IP address of the terminal device.
130. A communications device, comprising: The communication device is a first network element in a core network, comprising: A sending unit, configured to send a first message to a terminal device, the first message comprising an address of the terminal device, the address of the terminal device being used for transmission of signaling between the terminal device and the core network.
131. The communication device of claim 130, wherein, The sending unit is configured to: Send a second message to a second network element in the core network, the second message comprising an identifier of the terminal device and an address of the terminal device.
132. The communication device of claim 131, wherein, The second network element comprises a unified data management function and / or a unified data repository.
133. The communication device of any one of claims 130-132, wherein, The sending unit is configured to send a third message to a server, the third message being used to request the server to allocate an address for the terminal device; The receiving unit is configured to receive the address of the terminal device sent by the server.
134. The communication device of claim 133, wherein, The third message comprises an identifier of the terminal device and / or slice information of the terminal device.
135. The communication device of claim 133 or 134, wherein, The third message is sent after the terminal device successfully registers with the core network.
136. The communication device of any one of claims 130 to 135, wherein, The first message further comprises one or more of the following: an identifier of the terminal device; an address and / or FQDN of a third network element in the core network, the third network element being configured to discover other network elements in the core network; addresses and / or FQDNs of one or more fourth network elements in the core network, the fourth network elements being network elements in the core network configured to serve the terminal device; security parameters for the terminal device to establish a security context with network elements in the core network; slice information.
137. The communication device of claim 136, wherein, The third network element is a network repository function.
138. The communication device of any one of claims 130 to 137, wherein, The address of the terminal device and the address of the access network device belong to different address sets.
139. The communication device of any one of claims 130 to 138, wherein, The address of the terminal device is an IP address of the terminal device.
140. A communications device, comprising: The communication device is a second network element in the core network, comprising: a receiving unit configured to receive a second message, the second message comprising an identifier of a terminal device and an address of the terminal device, the address of the terminal device being used for signaling transmission between the terminal device and the core network.
141. The communication device of claim 140, wherein, The second network element is a unified data management function and / or a unified data repository.
142. A terminal device, comprising: comprising: a sending unit configured to send a fifth message to a target network element, the fifth message being used to indicate that the terminal device supports address-based signaling transmission.
143. The terminal device of claim 142, wherein, The terminal device further comprises: a first receiving unit configured to receive a sixth message sent by the target network element, the sixth message being used to indicate one or more of the following: the target network element supports address-based signaling transmission; the target network element accepts address-based signaling transmission; the target network element does not support address-based signaling transmission; the target network element rejects address-based signaling transmission.
144. The terminal device of claim 142 or 143, wherein, The target network element is an access network device.
145. The terminal device of claim 144, wherein, The terminal device further comprises: a second receiving unit configured to receive broadcast information sent by the target network element, the broadcast information being used to indicate that the target network element supports address-based signaling transmission.
146. The terminal device of claim 145, wherein, The broadcast information is carried in a system information block.
147. The terminal device of claim 142 or 143, wherein, The target network element is a network element in the core network.
148. The terminal device of claim 147, wherein, The target network element is an authentication server function or a mobility management network element.
149. The terminal device of any one of claims 142 to 148, wherein, The fifth message is a registration request message.
150. The terminal device of any one of claims 142 to 149, wherein, The address is an IP address.
151. A communications device, characterized by The communication device is a target network element, comprising: a receiving unit configured to receive a fifth message sent by a terminal device, the fifth message being used to indicate that the terminal device supports address-based signaling transmission.
152. The communication device of claim 151, wherein, The communication device further comprises: a first sending unit configured to send a sixth message to the terminal device, the sixth message being used to indicate one or more of the following: the target network element supports address-based signaling transmission; the target network element accepts address-based signaling transmission; the target network element does not support address-based signaling transmission; the target network element rejects address-based signaling transmission.
153. The communication device of claim 151 or 152, wherein, The target network element is an access network device.
154. The communication device of claim 153, wherein, The communication device further comprises: The second sending unit is configured to send broadcast information to the terminal device, where the broadcast information is used to indicate that the target network element supports address-based signaling transmission.
155. The communication device of claim 154, wherein, The broadcast information is carried in a system information block.
156. The communication device of claim 151 or 152, wherein, The target network element is a network element in a core network.
157. The communication device of claim 156, wherein, The target network element is an authentication service function or a mobility management network element.
158. The communication device of any one of claims 151 to 157, wherein, The fifth message is a registration request message.
159. The communication device of any one of claims 151 to 158, wherein, The address is an IP address.
160. A communications device, comprising: The communication device is an access network device, and the communication device comprises: The receiving unit is configured to receive a seventh message sent by the terminal device, where the seventh message comprises one or more of the following: first NAS signaling, which is NAS signaling sent by the terminal device to a fourth network element in a core network; an address of the terminal device; and an address of the fourth network element.
161. The communication device of claim 160, wherein, The communication device further comprises: After receiving the seventh message, the first sending unit is configured to send a first data packet to the fourth network element, where the first data packet is an address-based data packet, and the first data packet comprises the first NAS signaling.
162. The communication device of claim 160 or 161, wherein, The seventh message comprises a first NAS container, and the first NAS signaling is carried in the first NAS container.
163. The communication device of any one of claims 160 to 162, wherein, The seventh message is an RRC message.
164. The communication device of any one of claims 160 to 163, wherein, The first data packet comprises one or more of the following: an address of the access network device; an address of the fourth network element; and an address of the terminal device.
165. The communication device of claim 164, wherein, The first data packet comprises a first packet header and / or a second packet header, where a source address of the first packet header is an address of the access network device, a destination address of the first packet header is an address of the fourth network element, a source address of the second packet header is an address of the terminal device, and a destination address of the second packet header is an address of the fourth network element.
166. The communication device of any one of claims 160 to 165, wherein, The receiving unit is configured to receive a second data packet sent by the fourth network element, where the second data packet is an address-based data packet, and the second data packet comprises second NAS signaling, which is NAS signaling sent by the fourth network element in response to the first NAS signaling.
167. The communication device of claim 166, wherein, The second data packet comprises one or more of the following:
168. The communication device of claim 167, wherein, an address of the access network device; 169. The communication device of any one of claims 166 to 168, wherein, an address of the fourth network element; and an address of the terminal device.
170. The communication device of claim 169, wherein, The second data packet comprises a third packet header and / or a fourth packet header, where a source address of the third packet header is an address of the fourth network element, a destination address of the third packet header is an address of the access network device, a source address of the fourth packet header is an address of the fourth network element, and a destination address of the fourth packet header is an address of the terminal device.
171. The communication device of claim 169 or 170, wherein, The communication device further comprises:
172. The communication device of any one of claims 169 to 171, wherein, The second sending unit is configured to send an eighth message to the terminal device, where the eighth message comprises the second NAS signaling. The eighth message further comprises an address of the terminal device and / or an address of the fourth network element. The eighth message comprises a second NAS container, and the second NAS signaling is carried in the second NAS container. The eighth message is an RRC message.
173. The communication device according to any one of claims 160 to 172, wherein The receiving unit is configured to receive a ninth message sent by the terminal device, the ninth message containing first information, and the first information being used to request an address of the fourth network element from a third network element of the core network. The third sending unit is configured to send a third data packet to the third network element, the third data packet being a data packet based on address transmission, and the third data packet containing the first information.
174. The communication device of claim 173, wherein, The first information contains one or more of the following: an identifier of the terminal device; a type of the fourth network element; an FQDN of the fourth network element; slice information.
175. The communication device of claim 174, wherein, The ninth message contains a third NAS container, and the first information is carried in the third NAS container.
176. The communication device of any one of claims 173 to 175, wherein, The ninth message further includes an address of the terminal device and / or an address of the third network element.
177. The communication device of any one of claims 173 to 176, wherein, The ninth message is an RRC message.
178. The communication device of any one of claims 173 to 177, wherein, The third data packet further includes one or more of the following: an address of the access network device; an address of the third network element; an address of the terminal device.
179. The communication device of claim 178, wherein, The third data packet includes a fifth packet header and / or a sixth packet header, a source address of the fifth packet header being an address of the access network device, a destination address of the fifth packet header being an address of the third network element, a source address of the sixth packet header being an address of the terminal device, and a destination address of the sixth packet header being an address of the third network element.
180. The communication device of any one of claims 173-179, wherein, The receiving unit is configured to receive a fourth data packet sent by the third network element, the fourth data packet being a data packet based on address transmission, and the fourth data packet containing one or more of the following: an address of the fourth network element; an FQDN of the fourth network element; a type of the fourth network element; an identifier of the terminal device; an address of the terminal device; an address of the access network device; slice information.
181. The communication device of claim 180, wherein, The fourth data packet includes a seventh packet header and / or an eighth packet header, a source address of the seventh packet header being an address of the third network element, a destination address of the seventh packet header being an address of the access network device, a source address of the eighth packet header being an address of the third network element, and a destination address of the eighth packet header being an address of the terminal device.
182. The communication device of claim 160 or 181, wherein, The communication device further includes: a fourth sending unit configured to send second information to a fifth network element of the core network, the second information being used to request an identifier of the terminal device, and the second information containing an address of the terminal device; The receiving unit is configured to receive an identifier of the terminal device sent by the fifth network element.
183. The communication device of any one of claims 173 to 182, wherein, The communication device further includes: a fifth sending unit configured to send a tenth message to the terminal device, the tenth message containing one or more of the following: an address of the fourth network element; an FQDN of the fourth network element; a type of the fourth network element; an identifier of the terminal device; an address of the terminal device.
184. The communication device of claim 183, wherein, The tenth message contains a fourth NAS container, and the address of the fourth network element is carried in the fourth NAS container.
185. The communication device of claim 183 or 184, wherein, The tenth message is an RRC message.
186. The communication device of any one of claims 160 to 185, wherein, The first data packet is an IP data packet.
187. A terminal device, comprising: The communication device further includes: The sending unit is configured to send a seventh message to the access network device, the seventh message comprising one or more of the following: first NAS signaling, the first NAS signaling being NAS signaling sent by the terminal device to a fourth network element in the core network; an address of the terminal device; an address of the fourth network element.
188. The terminal device of claim 187, wherein, The seventh message comprises a first NAS container, and the first NAS signaling is carried in the first NAS container.
189. The terminal device of claim 187 or 188, wherein, The seventh message is an RRC message.
190. The terminal device of any one of claims 187 to 189, wherein, The terminal device further comprises: a first receiving unit configured to receive an eighth message sent by the access network device, the eighth message comprising second NAS signaling, the second NAS signaling being NAS signaling sent by the fourth network element in response to the first NAS signaling.
191. The terminal device of claim 190, wherein, The eighth message further comprises an address of the terminal device and / or an address of the fourth network element.
192. The terminal device of claim 190 or 191, wherein, The eighth message comprises a second NAS container, and the second NAS signaling is carried in the second NAS container.
193. The terminal device of any one of claims 190 to 192, wherein, The eighth message is an RRC message.
194. The terminal device of any one of claims 187 to 193, wherein, The sending unit is configured to send a ninth message to the access network device, the ninth message comprising first information, the first information being used to request an address of the fourth network element from a third network element of the core network.
195. The terminal device of claim 194, wherein, The first information comprises one or more of the following: an identifier of the terminal device; a type of the fourth network element; an FQDN of the fourth network element; slice information.
196. The terminal device of claim 195, wherein, The ninth message comprises a third NAS container, and the first information is carried in the third NAS container.
197. The terminal device of any one of claims 194 to 196, wherein, The ninth message further comprises an address of the terminal device and / or an address of the third network element.
198. The terminal device of any one of claims 194 to 197, wherein, The ninth message is an RRC message.
199. The terminal device of any one of claims 194 to 198, wherein, The terminal device further comprises: a second receiving unit configured to receive a tenth message sent by the access network device, the tenth message comprising one or more of the following: an address of the fourth network element; an FQDN of the fourth network element; a type of the fourth network element; an identifier of the terminal device; an address of the terminal device.
200. The terminal device of claim 199, wherein, The tenth message comprises a fourth NAS container, and the address of the fourth network element is carried in the fourth NAS container.
201. The terminal device of claim 199 or 200, wherein, The tenth message is an RRC message.
202. The terminal device of any one of claims 187 to 201, wherein, The address of the terminal device is an IP address.
203. A communications device, characterized by The communication device is a fourth network element in a core network, comprising: a receiving unit configured to receive a first data packet sent by an access network device, the first data packet being a data packet transmitted based on an address, and the first data packet comprising first NAS signaling sent by a terminal device to the fourth network element.
204. The communication device of claim 203, wherein, The first data packet comprises one or more of the following: an address of the access network device; an address of the fourth network element; an address of the terminal device.
205. The communication device of claim 204, wherein, The first data packet comprises a first packet header and / or a second packet header, a source address of the first packet header being an address of the access network device, a destination address of the first packet header being an address of the fourth network element, a source address of the second packet header being an address of the terminal device, and a destination address of the second packet header being an address of the fourth network element.
206. The communication device of any one of claims 203 to 205, wherein, The communication device further comprises: a sending unit, configured to send a second data packet to the access network device, the second data packet being an address-based transmission data packet, and the second data packet containing second NAS signaling, the second NAS signaling being NAS signaling sent by the fourth network element in response to the first NAS signaling.
207. The communication device of claim 206, wherein, The second data packet comprises one or more of the following: an address of the access network device; an address of the fourth network element; an address of the terminal device.
208. The communication device of claim 207, wherein, The second data packet comprises a third packet header and / or a fourth packet header, a source address of the third packet header being an address of the fourth network element, a destination address of the third packet header being an address of the access network device, a source address of the fourth packet header being an address of the fourth network element, and a destination address of the fourth packet header being an address of the terminal device.
209. The communication device of any one of claims 203 to 208, wherein, The first data packet is an IP data packet.
210. A communications device, characterized by The communication device is a third network element of a core network, comprising: a receiving unit, configured to receive a third data packet sent by an access network device, the third data packet being an address-based transmission data packet, and the third data packet containing first information, the first information being used to request an address of a fourth network element in the core network from the third network element.
211. The communication device of claim 210, wherein, The first information comprises one or more of the following: an identifier of the terminal device; a type of the fourth network element; an FQDN of the fourth network element; slice information.
212. The communication device of claim 210 or 211, wherein, The third data packet further comprises one or more of the following: an address of the access network device; an address of the third network element; an address of the terminal device.
213. The communication device of claim 212, wherein, The third data packet comprises a fifth packet header and / or a sixth packet header, a source address of the fifth packet header being an address of the access network device, a destination address of the fifth packet header being an address of the third network element, a source address of the sixth packet header being an address of the terminal device, and a destination address of the sixth packet header being an address of the third network element.
214. The communication device of any one of claims 210 to 213, wherein, The communication device further comprises: a sending unit, configured to send a fourth data packet to the access network device, the fourth data packet being an address-based transmission data packet, and the fourth data packet containing one or more of the following: an address of the fourth network element; an FQDN of the fourth network element; an identifier of the terminal device; an address of the terminal device; an address of the access network device; slice information.
215. The communication device of claim 93, wherein, The fourth data packet comprises a seventh packet header and / or an eighth packet header, a source address of the seventh packet header being an address of the third network element, a destination address of the seventh packet header being an address of the access network device, a source address of the eighth packet header being an address of the third network element, and a destination address of the eighth packet header being an address of the terminal device.
216. The communication device of any one of claims 210 to 215, wherein, The third data packet is an IP data packet.
217. A communications device, characterized by The communication device is an access network device, comprising: a receiving unit, configured to receive a fifth data packet sent by a fourth network element in a core network, the fifth data packet being an address-based transmission data packet, and the fifth data packet containing third NAS signaling, the third NAS signaling being NAS signaling sent by the fourth network element to a terminal device.
218. The communication device of claim 217, wherein, The fifth data packet further comprises one or more of the following: an address of the fourth network element; an address of the terminal device; an address of the access network device; slice information.
219. The communication device of claim 218, wherein, The fifth data packet comprises a ninth packet header and / or a tenth packet header, a source address of the ninth packet header is an address of the fourth network element, a destination address of the ninth packet header is an address of the access network device, a source address of the tenth packet header is an address of the fourth network element, and a destination address of the tenth packet header is an address of the terminal device.
220. The communication device of any one of claims 217 to 219, wherein, The communication device further comprises: a sending unit configured to send an eleventh message to the terminal device, the eleventh message comprising one or more of the following: the third NAS signaling; an address of the fourth network element; an address of the terminal device.
221. The communication device of claim 220, wherein, The eleventh message comprises a fifth NAS container, and the third NAS signaling is carried in the fifth NAS container.
222. The communication device of claim 220 or 221, wherein, The eleventh message is an RRC message.
223. The communication device of any of claims 220-222, wherein, if the terminal device is in an idle state, the sending unit is configured to send a paging message to the terminal device, the paging message comprising an identifier of the terminal device.
224. The communication device of any one of claims 217 to 223, wherein, The fifth data packet is an IP data packet.
225. A communications device, characterized by The communication device is a fourth network element in a core network, comprising: a sending unit configured to send a fifth data packet to an access network device, the fifth data packet being a data packet based on address transmission, and the fifth data packet comprising third NAS signaling, the third NAS signaling being NAS signaling sent by the fourth network element to a terminal device.
226. The communication device of claim 225, wherein, The fifth data packet further comprises one or more of the following: an address of the fourth network element; an address of the terminal device; an address of the access network device; slice information.
227. The communication device of claim 226, wherein, The fifth data packet comprises a ninth packet header and / or a tenth packet header, a source address of the ninth packet header is an address of the fourth network element, a destination address of the ninth packet header is an address of the access network device, a source address of the tenth packet header is an address of the fourth network element, and a destination address of the tenth packet header is an address of the terminal device.
228. The communication device of any one of claims 225 to 227, wherein, The sending unit is configured to send a twelfth message to a second network element of the core network, the twelfth message being used to request an address of the terminal device and / or an address of the access network device.
229. The communication device of claim 228, wherein: the twelfth message is used to request the address of the terminal device or the address of the access network device, and the twelfth message comprises an identifier of the terminal device; or the twelfth message is used to request the address of the access network device, and the twelfth message comprises an identifier of the terminal device and / or an address of the terminal device.
230. The communication device of claim 228 or 229, wherein, The communication device further comprises: a receiving unit configured to receive a thirteenth message sent by the second network element, the thirteenth message comprising one or more of the following: an address of the access network device; an identifier of the access network device; an identifier of the terminal device.
231. The communication device of any one of claims 228 to 230, wherein, The second network element comprises a unified data management function and / or a unified data repository.
232. The communication device of any one of claims 225 to 231, wherein, The fifth data packet is an IP data packet.
233. A communications device, characterized by The communication device is a second network element in a core network, comprising: The receiving unit is configured to receive a twelfth message sent by the fourth network element, the twelfth message being used to request an address of the terminal device and / or an address of an access network device serving the terminal device. The address of the terminal device is used for transmission of signaling between the terminal device and the core network.
234. The communication device of claim 233, wherein: The twelfth message is used to request the address of the terminal device or the address of the access network device, and the twelfth message comprises an identifier of the terminal device; or The twelfth message is used to request the address of the access network device, and the twelfth message comprises the identifier of the terminal device and / or the address of the terminal device.
235. The communication device of claim 233 or 234, wherein, The communication device further comprises: The sending unit is configured to send a thirteenth message to the fourth network element, the thirteenth message comprising one or more of the following: The address of the access network device; The identifier of the access network device; The identifier of the terminal device.
236. The communication device of any one of claims 233 to 235, wherein, The second network element comprises a unified data management function and / or a unified data repository.
237. The communication device of any one of claims 233 to 236, wherein, The address of the access network device is an IP address.
238. A terminal device, comprising: The receiving unit is configured to receive an eleventh message sent by an access network device, the eleventh message comprising one or more of the following: Third NAS signaling, the third NAS signaling being NAS signaling sent by a fourth network element in a core network to a terminal device; An address of the fourth network element; An address of the terminal device. The eleventh message comprises a fifth NAS container, and the third NAS signaling is carried in the fifth NAS container.
239. The terminal device of claim 238, wherein, The eleventh message is an RRC message.
240. The terminal device of claim 238 or 239, wherein, The receiving unit is configured to receive a paging message sent by the access network device, the paging message comprising an identifier of the terminal device.
241. The terminal device of any one of claims 238 to 240, wherein, The address of the terminal device is an IP address.
242. The terminal device of any one of claims 238 to 241, wherein, The terminal device comprises a transceiver, a memory, and a processor. The memory is configured to store a program. The processor is configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the terminal device performs one of the following: the method of any one of claims 1-8, the method of any one of claims 21-29, the method of any one of claims 66-81, or the method of any one of claims 117-121.
243. A terminal device, comprising: The network device comprises a transceiver, a memory, and a processor. The memory is configured to store a program. The processor is configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the network device performs one of the following: the method of any one of claims 9-18, the method of any one of claims 19-20, the method of any one of claims 30-38, the method of any one of claims 39-65, the method of any one of claims 82-88, the method of any one of claims 89-95, the method of any one of claims 96-103, the method of any one of claims 104-111, or the method of any one of claims 112-116.
244. A network device, comprising: 245. An apparatus, comprising: including a processor to call a program from a memory to cause the apparatus to perform the method of any of claims 1-121.
246. A chip, characterized by including a processor to call a program from a memory to cause the apparatus to perform the method of any of claims 1-121.
247. A computer-readable storage medium, characterized in that, having a program stored thereon, the program causing a computer to perform the method of any of claims 1-121.
248. A computer program product, characterized in that, including a program to cause a computer to perform the method of any of claims 1-121.
249. A computer program characterised in that, the computer program causing a computer to perform the method of any of claims 1-121.
Citation Information
Patent Citations
Communication method and device
CN113329448A
Communication method and device
CN113498193A
IP address allocation method and device
WO2018058620A1
Wireless communication schemes for supporting connections with internet protocol
WO2024055336A1