Wireless communication method, communication device and communication system

Abstract

The present application provides a wireless communication method, communication device, and communication system. The method includes: obtaining subnet information of a first subnet corresponding to a first session; receiving a data packet, which is a multicast packet or a broadcast packet; determining, based on the subnet information, that the data packet corresponds to the first session within the first subnet; and sending the data packet through the first session. Through this method, a user-plane network element can obtain the correspondence between the subnet information of the first session and the first subnet, thereby being able to send the received multicast packet or broadcast packet through the session within the subnet at the subnet granularity, thereby achieving accurate data packet transmission.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a wireless communication method, a communication device, and a communication system. Background Art

[0002] After registering with the network, the terminal can initiate a session with the network, and the terminal and the network can subsequently communicate through the established session.

[0003] When a user-plane network element receives a multicast packet or a broadcast packet, there is currently no good method for determining through which sessions the user-plane network element sends the multicast packet or the broadcast packet. Summary of the Invention

[0004] Embodiments of the present application provide a wireless communication method, a communication device, and a communication system for sending multicast packets or broadcast packets according to subnet granularity, thereby achieving accurate sending of multicast packets or broadcast packets.

[0005] In a first aspect, embodiments of the present application provide a wireless communication method, which can be performed by a user-plane network element or a module (e.g., a chip) within the user-plane network element. The method includes: obtaining subnet information of a first subnet corresponding to a first session; receiving a data packet, which is a multicast packet or a broadcast packet; determining, based on the subnet information, that the data packet corresponds to the first session within the first subnet; and sending the data packet via the first session.

[0006] Through the above method, the user-plane network element can obtain the correspondence between the first session and the subnet information of the first subnet, so that the received multicast packet or broadcast packet can be sent through the corresponding session according to the subnet granularity, thereby achieving accurate sending of the data packet.

[0007] In one possible implementation, the subnet information corresponding to the source IP address in the data packet is determined; if the subnet information corresponding to the first session is the same as the subnet information corresponding to the source IP address, the data packet is determined to correspond to the first session. This method can accurately determine the session to which the data packet corresponds.

[0008] In a possible implementation method, a packet detection rule is received from a session management network element, where the packet detection rule includes the subnet information.

[0009] In one possible implementation method, indication information is received from the session management network element; based on the indication information, a data packet configuring IP information for the first session is detected, wherein the data packet configuring IP information for the first session includes IP information corresponding to the first session, and the first session is an Ethernet type session; the IP information is sent to the session management network element, and the IP information is used to determine the subnet information.

[0010] In one possible implementation, the identifier of a first VLAN in the data packet is obtained; a VLAN set is obtained, the VLAN set including one or more VLANs in the first subnet; and if the first VLAN belongs to the VLAN set, the data packet is determined to correspond to the first session. This method can accurately determine the session to which the data packet corresponds.

[0011] In a possible implementation method, a packet detection rule is received from a session management network element, where the packet detection rule includes the VLAN set.

[0012] In a second aspect, embodiments of the present application provide a wireless communication method, which can be performed by a session management network element or a module (e.g., a chip) within the session management network element. The method includes: obtaining subnet information of a first subnet corresponding to a first session; and sending the subnet information to a user plane network element, where the subnet information is used to detect data packets matching the subnet information.

[0013] In a possible implementation method, a packet detection rule is sent to a user plane network element, where the packet detection rule includes the subnet information.

[0014] In one possible implementation method, an indication message is sent to a user plane network element, where the indication message indicates that a data packet configuring IP information for the first session is detected, where the first session is an Ethernet type session; IP information corresponding to the first session is received from the user plane network element; and the subnet information is determined based on the IP information.

[0015] In a possible implementation method, the subnet information is received from an authentication, authorization and accounting server.

[0016] In a possible implementation method, the subnet information is requested from the authentication, authorization and accounting server.

[0017] In a possible implementation method, the subnet information is received from a terminal.

[0018] In a third aspect, embodiments of the present application provide a wireless communication method, which can be performed by a terminal, a module in a terminal (such as a chip or modem), a device including terminal functions, an authentication, authorization, and billing server, or a module in an authentication, authorization, and billing server (such as a chip). The method includes: obtaining subnet information of a first subnet corresponding to a first session; and sending the subnet information to a session management network element, where the subnet information is used to detect data packets matching the subnet information.

[0019] In a possible implementation method, the subnet information is received from an authentication, authorization, and accounting server or a DHCP server.

[0020] In a fourth aspect, an embodiment of the present application provides a communication device, which may be a user plane network element or a module (such as a chip) in a user plane network element. The device has the function of implementing any implementation method of the first aspect described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0021] In a fifth aspect, an embodiment of the present application provides a communication device, which may be a session management network element or a module (such as a chip) in a session management network element. The device has the function of implementing any implementation method of the second aspect described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0022] In a sixth aspect, an embodiment of the present application provides a communication device, which may be a terminal, a module in a terminal (such as a chip or modem), a device containing terminal functions, an authentication authorization and billing server, or a module in an authentication authorization and billing server (such as a chip). The device has the function of implementing any implementation method of the third aspect described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0023] In a seventh aspect, an embodiment of the present application provides a communication device, comprising a module for executing any implementation method in the above-mentioned first to third aspects.

[0024] In an eighth aspect, an embodiment of the present application provides a communication device, comprising a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement any implementation method in the above-mentioned first to third aspects through a logic circuit or executing code instructions.

[0025] In a ninth aspect, an embodiment of the present application provides a communication device, comprising a processor coupled to a memory, the processor configured to call a program stored in the memory to execute any of the implementation methods described in aspects 1 to 3 above. The memory may be located within or outside the device, and the processor may be one or more.

[0026] In the tenth aspect, an embodiment of the present application provides a communication device, comprising a processor and a memory; the memory is used to store computer instructions, and when the communication device is running, the processor executes the computer instructions stored in the memory to enable the communication device to execute any implementation method in the above-mentioned first to third aspects.

[0027] In the eleventh aspect, an embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a communication device, it implements any implementation method in the above-mentioned first aspect or second aspect.

[0028] In the twelfth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed by a communication device, any implementation method in the above-mentioned first to third aspects is implemented.

[0029] In a thirteenth aspect, an embodiment of the present application further provides a communication system, which includes a communication device for executing any implementation method of the above-mentioned first aspect and a communication device for executing any implementation method of the above-mentioned second aspect.

[0030] In a possible implementation method, the communication system further includes a communication device for executing any implementation method of the third aspect above.

[0031] In the fourteenth aspect, an embodiment of the present application further provides a communication system, which includes a communication device for executing any implementation method of the above-mentioned second aspect and a communication device for executing any implementation method of the above-mentioned third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1(a) is a schematic diagram of the 5G network architecture based on service-oriented architecture;

[0033] Figure 1(b) is a schematic diagram of the 5G network architecture based on point-to-point interfaces;

[0034] Figure 2 This is an example diagram of a Class B IP address;

[0035] Figure 3 This is a schematic diagram of a subnet mask format for a Class B address;

[0036] Figure 4 This is another subnet mask format diagram for Class B addresses;

[0037] Figure 5 This is an example diagram of the relationship between IP subnets and sessions;

[0038] Figure 6 This is an example diagram of the relationship between VLAN and IP subnet;

[0039] Figure 7 A schematic diagram of a wireless communication method provided in an embodiment of the present application;

[0040] Figure 8 A schematic diagram of a wireless communication method provided in an embodiment of the present application;

[0041] Figure 9 A schematic diagram of a wireless communication method provided in an embodiment of the present application;

[0042] Figure 10 A schematic diagram of a wireless communication method provided in an embodiment of the present application;

[0043] Figure 11 A schematic diagram of a wireless communication method provided in an embodiment of the present application;

[0044] Figure 12 A schematic diagram of a communication device provided in an embodiment of the present application;

[0045] Figure 13 A schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of this application more clear, the application will be further described in detail below with reference to the accompanying drawings. The specific operation methods in the method embodiments can also be applied to the device embodiments or system embodiments.

[0047] Figure 1(a) illustrates the fifth-generation (5G) network architecture based on a service-oriented architecture. The 5G network architecture shown in Figure 1(a) includes three components: the terminal, the data network (DN), and the carrier network. The following briefly describes the functions of some of these network elements.

[0048] The operator network may include one or more of the following network elements: authentication server function (AUSF) network element, network exposure function (NEF) network element, policy control function (PCF) network element, unified data management (UDM) network element, unified data repository (UDR) network element, network repository function (NRF) network element, application function (AF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, radio access network (RAN) equipment, user plane function (UPF) network element, network slice selection function (NSSF) network element (not shown in the figure), etc. In the above-mentioned operator network, network elements or devices other than radio access network equipment can be referred to as core network network elements or core network equipment.

[0049] The wireless access network device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a next generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system, etc.; it can also be a module or unit that completes part of the functions of a base station, for example, a centralized unit (CU) or a distributed unit (DU). The wireless access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device. In the embodiments of the present application, a base station is used as an example of a wireless access network device for description.

[0050] A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal.

[0051] Base stations and terminals can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.

[0052] The AMF network element performs functions such as mobility management and access authentication / authorization. It is also responsible for transferring user policies between the terminal and the PCF.

[0053] The SMF network element performs functions such as session management, execution of control policies issued by the PCF, selection of the UPF, and allocation of Internet Protocol (IP) addresses for terminals.

[0054] The UPF network element, as the interface UPF with the data network, completes functions such as user plane data forwarding, session / flow-level billing statistics, and bandwidth limitation.

[0055] UDM network element performs functions such as managing contract data and user access authorization.

[0056] UDR performs access functions for contract data, policy data, application data, and other types of data.

[0057] NEF network element is used to support the opening of capabilities and events.

[0058] The AF network element conveys application-side requirements to the network, such as Quality of Service (QoS) requirements or user status event subscriptions. The AF can be a third-party functional entity or an application service deployed by the operator, such as the IP Multimedia Subsystem (IMS) voice call service.

[0059] The PCF network element is responsible for policy control functions such as session and service flow level billing, QoS bandwidth guarantee and mobility management, and terminal policy decision-making.

[0060] NRF network elements can be used to provide network element discovery capabilities, providing network element information corresponding to the network element type based on requests from other network elements. NRF also provides network element management services such as network element registration, update, and deregistration, as well as network element status subscription and push.

[0061] The AUSF network element is responsible for authenticating users to determine whether users or devices are allowed to access the network.

[0062] NSSF network element is used to select network slices, count users within the network slices, etc.

[0063] A DN is a network located outside of a carrier network. A carrier network can connect to multiple DNs, and a variety of services can be deployed on the DN, providing data and / or voice services to terminals. For example, a DN is the private network of a smart factory. Sensors installed in the workshop can be terminals, and the DN houses a control server for the sensors, which can provide services to the sensors. Sensors can communicate with the control server, receive instructions from the control server, and transmit collected sensor data to the control server based on the instructions. Another example is a DN that is a company's internal office network. An employee's mobile phone or computer can be a terminal, allowing them to access information and data resources on the company's internal office network.

[0064] In Figure 1(a), Nausf, Nnef, Npcf, Nudm, Naf, Namf, and Nsmf are service-oriented interfaces provided by the AUSF, NEF, PCF, UDM, AF, AMF, and SMF, respectively, for invoking corresponding service-oriented operations. N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers can be found in the definitions of the 3rd Generation Partnership Project (3GPP) standard protocols and are not limited here.

[0065] Figure 1(b) is a schematic diagram of a 5G network architecture based on point-to-point interfaces. The functions of the network elements in Figure 1(a) can be referred to for the functions of the corresponding network elements, and will not be repeated here. The main difference between Figure 1(b) and Figure 1(a) is that the interfaces between the control plane network elements in Figure 1(a) are service-oriented interfaces, while the interfaces between the control plane network elements in Figure 1(b) are point-to-point interfaces.

[0066] In the architecture shown in Figure 1(b), the interface names and functions between the various network elements are as follows:

[0067] 1) N1: The interface between AMF and the terminal, which can be used to deliver QoS control rules to the terminal.

[0068] 2) N2: The interface between AMF and RAN, which can be used to transmit radio bearer control information from the core network side to the RAN.

[0069] 3) N3: The interface between RAN and UPF, mainly used to transmit uplink and downlink user plane data between RAN and UPF.

[0070] 4) N4: The interface between SMF and UPF can be used to transmit information between the control plane and the user plane, including the control of the forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and the reporting of information on the user plane.

[0071] 5) N5: The interface between AF and PCF, which can be used to issue application service requests and report network events.

[0072] 6) N6: The interface between UPF and DN, used to transmit uplink and downlink user data flows between UPF and DN.

[0073] 7) N7: The interface between PCF and SMF, which can be used to issue protocol data unit (PDU) session granularity and service data flow granularity control strategy.

[0074] 8) N8: The interface between AMF and UDM, which can be used by AMF to obtain access and mobility management related subscription data and authentication data from UDM, as well as AMF to register the current mobility management related information of the terminal with UDM.

[0075] 9) N9: User plane interface between UPFs, used to transmit uplink and downlink user data flows between UPFs.

[0076] 10) N10: The interface between SMF and UDM, which can be used by SMF to obtain session management-related contract data from UDM, and SMF to register terminal current session related information with UDM.

[0077] 11) N11: The interface between SMF and AMF, which can be used to transmit PDU session tunnel information between RAN and UPF, transmit control messages sent to the terminal, transmit radio resource control information sent to RAN, etc.

[0078] 12) N12: The interface between AMF and AUSF, which can be used by AMF to initiate the authentication process to AUSF, which can carry SUCI as the contract identifier;

[0079] 13) N13: The interface between UDM and AUSF, which can be used by AUSF to obtain the user authentication vector from UDM to execute the authentication process.

[0080] 14) N15: The interface between PCF and AMF, which can be used to issue terminal policies and access control related policies.

[0081] 15) N35: The interface between UDM and UDR, which can be used by UDM to obtain user contract data information from UDR.

[0082] 16) N36: The interface between PCF and UDR, which can be used by PCF to obtain policy-related contract data and application data-related information from UDR.

[0083] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or function can be implemented by a single device, or by multiple devices, or can be a functional module within a single device, and this is not specifically limited in the embodiments of the present application.

[0084] The session management network element and user plane network element in this application may be the SMF and UPF in Figure 1(a) or Figure 1(b), respectively, or may be network elements having the functions of the SMF and UPF in future communications, such as sixth-generation (6G) networks. This application is not limited thereto. In the embodiments of this application, the SMF and UPF are used as examples of the session management network element and user plane network element, respectively.

[0085] In this application, an authentication, authorization and billing server is also deployed in the operator network or DN (not shown in Figure 1(a) and Figure 1(b)). The authentication, authorization and billing server is used to perform secondary authentication and authorization on the PDU session, and can provide the core network with the IP address of the PDU session, a list of media access control (MAC) addresses, a list of allowed virtual local area networks (VLANs), etc. The authentication, authorization and billing server in this application can be a data network authentication, authorization and accounting (DN-AAA) server, or it can be a network element with the functions of the above-mentioned authentication, authorization and billing server in future communications such as 6G networks. This application does not limit this. In the embodiments of this application, the DN-AAA server is described as an example of an authentication, authorization and billing server.

[0086] To facilitate understanding, some terms or nouns appearing in the embodiments of this application are first explained below.

[0087] 1. IP address

[0088] IP addresses can be divided into the following five categories:

[0089] Class A IP addresses: 0.0.0.0 to 127.255.255.255;

[0090] Class B IP addresses: 128.0.0.0 to 191.255.255.255;

[0091] Class C IP addresses: 192.0.0.0 to 233.255.255.255;

[0092] Class D IP addresses: 224.0.0.0 to 239.255.255.255;

[0093] Class E IP addresses: 240.0.0.0 to 247.255.255.255.

[0094] An IP address consists of a network ID, a subnet ID, and a host ID. For example, a Class A IP address has a network ID that occupies the first 8 bits of the IP address. A Class B IP address has a network ID that occupies the first 16 bits of the IP address. A Class C IP address has a network ID that occupies the first 24 bits of the IP address.

[0095] It should be noted that an IP address can be represented in multiple bases, such as binary, decimal, or hexadecimal. For example, an IP address represented in decimal as 140.252.254.100 would correspond to the binary representation of 10001100111111001111111001100100, and the hexadecimal representation of 0x8cfcfe64. For ease of explanation, the following uses decimal notation to represent an IP address.

[0096] Figure 2 This is an example diagram of a Class B IP address. For example, the network number of the Class B IP address occupies 16 bits, such as 140.252. Of the remaining 16 bits, the first 8 bits are the subnet number and the last 8 bits are the host number.

[0097] The network number can also be called the IP network number, the subnet number can also be called the IP subnet number, and the host number can also be called the IP host number. Two IP addresses with the same network number and subnet number are said to belong to the same IP subnet. For example, IP address 1 is 140.252.254.1, IP address 2 is 140.252.254.2, and IP address 3 is 140.252.253.3. When these three IP addresses are represented in binary format, the first 24 bits of each are used to represent the network number and subnet number. That is, 140.252 in IP address 1 represents the network number and subnet number of IP address 1, 140.252 in IP address 2 represents the network number and subnet number of IP address 2, and 140.252 in IP address 3 represents the network number and subnet number of IP address 3. Therefore, IP address 1 and IP address 2 belong to the same IP subnet, IP address 1 and IP address 3 belong to different IP subnets, and IP address 2 and IP address 3 belong to different IP subnets.

[0098] 2. Subnet Mask

[0099] The subnet mask occupies 32 bits and is used to indicate the number of bits occupied by the subnet ID and host ID in an IP address. For example, the bits with a value of 1 in the subnet mask are reserved for the network ID and subnet ID, and the bits with a value of 0 in the subnet mask are reserved for the host ID.

[0100] Figure 3The following diagram shows a subnet mask format for a Class B address. This subnet mask is represented in binary as 111111111111111111111111111000000000, or in decimal as 255.255.255.0 or hexadecimal as 0xffffff00. Because the network ID of a Class B address occupies 16 bits, this subnet mask indicates that the first 16 bits of the IP address are used for the network ID, the first 8 bits of the last 16 bits are used for the subnet ID, and the last 8 bits of the last 16 bits are used for the host ID.

[0101] Figure 4 The following is another subnet mask format diagram for a Class B address. This subnet mask is represented in binary as 11111111111111111111111111111000000, or in decimal as 255.255.255.192, or in hexadecimal as 0xffffffc0. This subnet mask indicates that the first 16 bits of the IP address are used for the network ID, the first 10 bits of the last 16 bits are used for the subnet ID, and the last 6 bits of the last 16 bits are used for the host ID.

[0102] In practical applications, an IP address and its subnet mask can be expressed in the format of "IP address / total number of bits of network number and subnet number." "IP address / total number of bits of network number and subnet number" can also be referred to as the IP address configuration information. For example, the configuration information for a Class B IP address is 140.252.254.1 / 24, indicating that the IP address is 140.252.254.1. The 24 indicates that the first 24 bits of the IP address, when expressed in binary format, are used to identify the network number and subnet number. This means that the subnet mask for this IP address is 255.255.255.0. It can be understood that " / 24" is a simplified representation of the subnet mask 255.255.255.0.

[0103] 3. Relationship between IP subnet and session

[0104] An IP subnet corresponds to one or more sessions. When an IP subnet corresponds to multiple sessions, the IP addresses of these sessions belong to the same IP subnet. Different sessions within the same IP subnet can belong to the same terminal or different terminals. Different sessions within different IP subnets can belong to the same terminal or different terminals.

[0105] Figure 5The following diagram illustrates the relationship between IP subnets and sessions. Sessions 1, 2, 3, and 4 correspond to IP subnet 1, while sessions 5, 6, and 7 correspond to IP subnet 2. The IP addresses of each session are shown in the diagram. Any two sessions from 1 to 7 can belong to the same terminal or different terminals. For example, sessions 1 and 2 belong to terminal 1, sessions 3 and 4 belong to terminal 2, session 5 belongs to terminal 3, and sessions 6 and 7 belong to terminal 4. Another example is sessions 1, 2, and 5 belong to terminal 1, sessions 3 and 4 belong to terminal 2, and sessions 6 and 7 belong to terminal 3.

[0106] 4. VLAN

[0107] Ethernet switches typically have dozens or even dozens of ports. By default, devices connected to these ports (such as terminals) can communicate unimpeded at Layer 2. However, in some cases, it is desirable to prevent devices on certain ports from being accessed by devices on other ports. In such cases, this default behavior cannot be used. Instead, a feature can be introduced that groups any number of ports on the switch together to form a closed system. Devices connected to this closed system can communicate with each other, but devices connected to this closed system cannot communicate at Layer 2 with devices not connected to it. This combination forms a virtual local area network (VLAN).

[0108] All devices within the same VLAN belong to the same IP subnet. This means that any two devices within the same VLAN have the same network ID and subnet ID in their IP addresses. Devices within different VLANs can belong to the same or different IP subnets.

[0109] Figure 6 The following diagram shows an example of the relationship between VLANs and IP subnets. In this example, VLAN 1, VLAN 2, VLAN 3, and VLAN 4 all correspond to IP subnet 1, VLAN 5 and VLAN 6 all correspond to IP subnet 2, and VLAN 7, VLAN 8, and VLAN 9 all correspond to IP subnet 3. VLANs 1 through VLAN 9 are identified by VLAN ID 1 through VLAN ID 9, respectively.

[0110] Therefore, the IP addresses of sessions established by terminals in VLAN 1 to VLAN 4 all correspond to IP subnet 1, the IP addresses of sessions established by terminals in VLAN 5 and VLAN 6 all correspond to IP subnet 2, and the IP addresses of sessions established by terminals in VLAN 7 to VLAN 9 all correspond to IP subnet 3.

[0111] VLANs within the same IP subnet can form a VLAN set. For example, VLANs 1 to VLAN 4 form VLAN set 1, VLANs 5 and VLAN 6 form VLAN set 2, and VLANs 7 to VLAN 9 form VLAN set 3.

[0112] V. Unicast, Multicast, and Broadcast

[0113] Unicast refers to a one-to-one communication mode between devices (such as terminals). Devices in the network communicate through routing nodes (such as switches or routers). After the sending device sends data to the routing node, the routing node only forwards the data without copying it. If 10 receiving devices need the same data, the sending device needs to transmit it one by one, repeating the same operation 10 times. However, due to its ability to respond promptly to the requirements of each device, web browsing now generally uses unicast mode. Routers and switches in the network select the transmission path based on the target IP address and transmit unicast data to the device corresponding to the target IP address. A unicast IP address is the IP address of a single device.

[0114] Multicast refers to a one-to-one communication mode between devices. Devices that join the same group can receive data within that group. Network switches and routers replicate and forward only the data they need to those who request it. Devices can request to join or leave a group. Routers and switches selectively replicate and transmit data, transmitting only to devices within the group. This allows data to be transmitted to multiple devices in a group simultaneously while ensuring that communications with devices outside the group are not affected. Multicast IP addresses are typically Class D IP addresses.

[0115] Broadcast refers to a one-to-all communication mode between devices. The network unconditionally replicates and forwards data sent by every device, allowing all devices to receive broadcast data. Because no path selection is required, network costs are low. Cable television networks are typical broadcast networks; a television receives signals from all channels but only reproduces the signal from one channel. Broadcast is also permitted in data networks, but is typically confined to the local area network (LAN) of a Layer 2 switch. Broadcast data is prohibited from traversing routers to prevent it from affecting a large number of devices. There are four types of broadcast IP addresses: 1) a restricted broadcast address (255.255.255.255); 2) a network-directed broadcast address (with a host ID of all 1s); 3) a subnet-directed broadcast address (with a host ID of all 1s and a specific subnet ID); and 4) a broadcast address (with both the subnet ID and host ID of all 1s and a specific network ID).

[0116] Currently, when a terminal initiates a session with the network, an IP address is allocated for that session. If multiple sessions are established on the terminal, an IP address is allocated for each session. The IP address for the terminal's session can be allocated by a core network element (such as the SMF or UPF) or by other devices (such as a DN-AAA server or a Dynamic Host Configuration Protocol (DHCP) server).

[0117] At present, a possible method for sending data packets (which can be multicast packets or broadcast packets) is: the network element of the core network, such as UPF, sends data packets to the terminals associated with the DNN according to the DNN granularity. For example, the IP address of session 1 of terminal 1 and the IP address of session 2 of terminal 2 both belong to IP subnet 1, the IP address of session 3 of terminal 3, the IP address of session 4 of terminal 4, the IP address of session 5 of terminal 5, and the IP address of session 6 of terminal 6 all belong to IP subnet 2, and session 1 of terminal 1, session 2 of terminal 2, session 3 of terminal 3, and session 4 of terminal 4 all correspond to DNN 1, and session 5 of terminal 5 and session 6 of terminal 6 correspond to DNN2. When the UPF receives a data packet, it first determines the DNN to which the data packet corresponds. Then it sends the data packet to the session corresponding to the DNN.

[0118] For example, the UPF receives a data packet from IP subnet 1, and the data packet corresponds to DNN 1. The UPF then determines the sessions corresponding to DNN 1, such as session 1, session 2, session 3, and session 4, and then sends the data packet to session 1, session 2, session 3, and session 4. This method shows that the UPF sends data packets to both sessions in IP subnet 1 and sessions in IP subnet 2. However, in reality, the data packet from IP subnet 1 may only need to be sent to sessions of terminals within IP subnet 1. Since multicast or broadcast packets cannot be sent according to IP subnet granularity (or subnet granularity), multicast or broadcast packets may be mistakenly sent to certain terminals, resulting in a waste of core network and air interface resources and creating security risks.

[0119] For example, the UPF receives a packet from IP subnet 2, corresponding to DNN 2. The UPF then determines the sessions corresponding to DNN 2, such as Session 5 and Session 6, and sends the packet to Sessions 5 and 6. This method demonstrates that the UPF only sends the packet to Sessions 5 and 6 within IP subnet 2, and not to Sessions 3 and 4 within IP subnet 2. This means that the packet cannot be sent at the IP subnet granularity. Since multicast or broadcast packets cannot be sent at the IP subnet granularity, this may result in multicast or broadcast packets not being delivered to certain terminals.

[0120] In response to the current problem of being unable to send multicast packets or broadcast packets according to the IP subnet granularity, the solution provided by the embodiment of the present application is: the network element of the core network, such as SMF, obtains the IP subnet information of the terminal session, and then configures the IP subnet information of the terminal session to the UPF, so that the UPF can match the received data packet (which can be a multicast packet or a broadcast packet) with the IP subnet information of the terminal session. If the data packet received by the UPF matches the IP subnet information of the terminal session, the data packet is sent through the session of the terminal. Based on this method, the UPF can determine the IP subnet corresponding to the received data packet, and then send the data packet through the session of the terminal in the IP subnet, thereby realizing the sending of data packets according to the IP subnet granularity.

[0121] The various wireless communication methods provided in the embodiments of the present application can be respectively performed by a UPF or a module (such as a chip) in a UPF, an SMF or a module (such as a chip) in an SMF, a DN-AAA or a module (such as a chip) in a DN-AAA, and a terminal, a module (such as a chip or a modem) in a terminal, or a device including terminal functions. For ease of explanation, the following description takes the UPF, SMF, DN-AAA, and terminal performing the wireless communication method as an example.

[0122] Figure 7 A schematic diagram of a wireless communication method provided in an embodiment of the present application. The method includes the following steps:

[0123] Step 701: SMF obtains subnet information of a first subnet corresponding to a first session.

[0124] The first session here may be an IP-type PDU session or an Ethernet-type PDU session.

[0125] The subnet information of the first subnet can be represented by network number + subnet number, or by IP address + subnet mask, or by the result of the operation of IP address and subnet mask. For example, the operation of IP address and subnet mask can be an AND operation of IP address and subnet mask. Taking the configuration information of the IP address of the first session as 140.252.254.1 / 24 as an example, the subnet information of the first subnet corresponding to the first session includes the network ID and subnet ID of the first subnet, that is, 140.252.254, or includes the IP address and subnet mask of the first subnet, that is, 140.252.254.1 and 255.255.255.0, or includes the calculation result of the IP address and subnet mask of the first subnet, that is, 140.252.254.0 / 24 (where 140.252.254.0 is the result of the "AND" operation of 140.252.254.1 and 255.255.255.0).

[0126] by Figure 5 For example, when the first session is Figure 5 If the first session is session 1, session 2, session 3 or session 4, the first subnet corresponding to the first session is determined to be IP subnet 1, and the subnet information of IP subnet 1 is 140.252.254.0 / 24. Figure 5 If it is session 5, session 6 or session 7 in the first session, it is determined that the first subnet corresponding to the first session is IP subnet 2, and the subnet information of IP subnet 2 is 140.252.253.0 / 24.

[0127] As an implementation method, the SMF can obtain the subnet information of the first subnet corresponding to the first session from the terminal. For example, the terminal requests the DHCP server or DN-AAA server to allocate an IP address for the first session through the user. The DHCP server or DN-AAA server allocates an IP address for the first session of the terminal based on the terminal's request, and sends a DHCP response or DN-AAA response to the terminal through the UPF. The DHCP response or DN-AAA response carries the configuration information of the IP address, so that the terminal can obtain the subnet information of the subnet corresponding to the first session based on the configuration information of the IP address. Subsequently, the terminal can actively send the subnet information of the first subnet corresponding to the first session to the SMF, or send the subnet information of the first subnet corresponding to the first session to the SMF based on the request of the SMF. For example, the terminal sends a NAS message to the SMF, which carries the identifier of the first session and the subnet information of the first subnet corresponding to the first session.

[0128] As another implementation method, the SMF may also obtain the subnet information of the first subnet corresponding to the first session from the DN-AAA server. That is, the DN-AAA server sends the subnet information of the first subnet corresponding to the first session to the SMF. Optionally, the SMF further requests the DN-AAA server to obtain the subnet information of the first subnet corresponding to the first session, and the DN-AAA server sends the subnet information of the first subnet corresponding to the first session to the SMF based on the SMF's request. Exemplarily, the SMF sends an authentication and authorization request to the DN-AAA server, which carries the terminal's generic public subscription identity (GPSI) and request ID. The DN-AAA server sends an authentication and authorization reply to the SMF, which carries the authentication and authorization result, IP address configuration information, and request ID. The SMF stores the correspondence between the identifier of the first session and the request ID. Therefore, the SMF can determine that the IP address configuration information in the authentication and authorization reply corresponds to the first session based on the request ID in the authentication and authorization reply. Then the SMF determines the subnet information of the IP address according to the configuration information of the IP address, and the subnet information is the subnet information of the first subnet corresponding to the first session.

[0129] As another implementation method, the SMF may also obtain the subnet information of the first subnet corresponding to the first session from the DHCP server. That is, the DHCP server sends the subnet information of the first subnet corresponding to the first session to the SMF. Optionally, the SMF further requests the DHCP server to obtain the subnet information of the first subnet corresponding to the first session, and the DHCP server sends the subnet information of the first subnet corresponding to the first session to the SMF based on the SMF's request. Exemplarily, the SMF sends a DHCP signaling request to the DHCP server, which carries a transaction identifier. The DHCP server sends a DHCP response to the SMF, which carries the configuration information of the IP address and the transaction identifier. The SMF stores the correspondence between the identifier of the first session and the transaction identifier, so the SMF can determine, based on the transaction identifier in the DHCP response, that the configuration information of the IP address in the DHCP response corresponds to the first session. The SMF then determines the subnet information of the IP address based on the configuration information of the IP address, and the subnet information is the subnet information of the first subnet corresponding to the first session.

[0130] As another implementation method, when the first session is an Ethernet-type session, the SMF may also obtain the subnet information of the first subnet corresponding to the first session from the UPF. For example, the SMF sends indication information to the UPF, for example, the indication information indicates the detection of a data packet configuring IP information for the first Ethernet-type session. Based on the indication information, the UPF detects the data packet configuring IP information for the first session, wherein the data packet configuring IP information for the first session includes IP information corresponding to the first session, for example, the IP information includes the IP address and subnet mask of the first session. Then, the UPF sends the IP information corresponding to the first session to the SMF, and the SMF determines the subnet information of the first subnet corresponding to the first session based on the IP information corresponding to the first session. For example, the IP information corresponding to the first session sent by UPF to SMF includes the IP address 140.252.254.1 and the subnet mask 255.255.255.0. The SMF determines that the subnet information of the first subnet corresponding to the first session is 140.252.254, or 140.252.254.0 / 24, or 140.252.254.1 and 255.255.255.0.

[0131] Step 702: UPF obtains subnet information of the first subnet corresponding to the first session from SMF.

[0132] That is, the SMF sends the subnet information of the first subnet corresponding to the first session to the UPF.

[0133] As an implementation method, the SMF may send a packet detection rule (PDR) to the UPF, which carries subnet information of the first subnet corresponding to the first session.

[0134] As another implementation method, the SMF may send a notification message to the UPF, which carries the subnet information of the first subnet corresponding to the first session.

[0135] Step 703: The UPF receives a data packet, which is a multicast packet or a broadcast packet.

[0136] The data packet received by the UPF may be an uplink data packet sent by a terminal, or a downlink data packet from a third-party server.

[0137] It should be noted that the order of step 702 and step 703 is not critical.

[0138] In step 704, the UPF determines that the data packet corresponds to the first session based on the subnet information of the first subnet.

[0139] As an implementation method, the UPF obtains the source IP address in the received data packet, determines the subnet information corresponding to the source IP address, and compares the subnet information corresponding to the source IP address with the subnet information of the first subnet corresponding to the first session. If the subnet information of the first subnet corresponding to the first session is the same as the subnet information corresponding to the source IP address, it is determined that the data packet corresponds to the first session. In other words, the correspondence between each session and the subnet information of the subnet is stored in the UPF. After the UPF determines the subnet information corresponding to the source IP address of the data packet, the session corresponding to the subnet information is determined based on the subnet information corresponding to the source IP address and the above-mentioned correspondence. For example, the source IP address corresponds to the subnet information of the first subnet, and the session corresponding to the subnet information of the first subnet can be called the first session. For example, there may be one or more first sessions corresponding to the data packet.

[0140] Among them, the method for UPF to determine the subnet information corresponding to the source IP address can be, for example: UPF performs an "AND" operation on the source IP address and the subnet mask corresponding to the IP address of the first session to obtain the subnet information corresponding to the source IP address. It should be noted that the subnet information corresponding to the source IP address may be the actual subnet information of the source IP address, or it may not be the actual subnet information of the source IP address. Figure 5 For example, if the source IP address in a received packet is 140.252.254.6, an AND operation is performed on this source IP address and the subnet mask corresponding to the IP address of session 1 (i.e., 255.255.255.0). The subnet information corresponding to the source IP address is 140.252.254.0 / 24, which means the network number is 140.252 and the subnet number is 254. Then, the subnet information corresponding to the source IP address is compared with the subnet information corresponding to session 1 (i.e., 140.252.254.0 / 24, which means the network number is 140.252 and the subnet number is 254). If the subnet information of the first subnet corresponding to session 1 is the same as the subnet information corresponding to the source IP address, the packet is determined to correspond to session 1. Similarly, the packet can be determined to correspond to sessions 2, 3, and 4. An AND operation is performed on the source IP address and the subnet mask corresponding to the IP address of session 5 (i.e., 255.255.255.0). The subnet information corresponding to the source IP address is 140.252.254.0 / 24, which means the network number is 140.252 and the subnet number is 254. The subnet information corresponding to the source IP address is then compared with the subnet information corresponding to session 5 (i.e., 140.252.253.0 / 24, which means the network number is 140.252 and the subnet number is 253). Because the subnet numbers are different, it is determined that the subnet information corresponding to the first subnet of session 5 is different from the subnet information corresponding to the source IP address. Therefore, the packet is determined not to correspond to session 5. Similarly, it can be determined that the packet does not correspond to session 6 or session 7.

[0141] As another implementation method, when the first session is an Ethernet type session, the UPF can obtain the identifier of the first VLAN in the received data packet, and obtain the VLAN set, which includes one or more VLANs under the first subnet corresponding to the first session. The UPF determines whether the first VLAN belongs to the VLAN set. If the first VLAN belongs to the VLAN set, it is determined that the data packet corresponds to the first session. If the first VLAN does not belong to the VLAN set, it is determined that the data packet does not correspond to the first session. Optionally, the UPF can receive the VLAN set from the SMF. For example, the SMF sends a PDR to the UPF, which carries the VLAN set. The IP addresses of the sessions of all terminals in the same VLAN correspond to the same IP subnet, that is, one VLAN corresponds to one IP subnet. The IP addresses of the sessions of terminals in different VLANs can correspond to the same IP subnet or different IP subnets, that is, different VLANs can correspond to the same IP subnet or different IP subnets. This is explained below with an example. Figure 6 For example, if the first session is a session under VLAN 1, VLAN 2, VLAN 3, or VLAN 4, the first session corresponds to IP subnet 1; if the first session is a session under VLAN 5 or VLAN 6, the first session corresponds to IP subnet 2; if the first session is a session under VLAN 7, VLAN 8, or VLAN 9, the first session corresponds to IP subnet 3. Therefore, if the first VLAN identifier in the data packet received by the UPF indicates VLAN 1, VLAN 2, VLAN 3, or VLAN 4, the UPF determines that the data packet corresponds to a session under VLAN 1, VLAN 2, VLAN 3, and VLAN 4; if the first VLAN identifier in the data packet received by the UPF indicates VLAN 5 or VLAN 6, the UPF determines that the data packet corresponds to a session under VLAN 5 and VLAN 6; if the first VLAN identifier in the data packet received by the UPF indicates VLAN 7, VLAN 8, or VLAN 9, the UPF determines that the data packet corresponds to a session under VLAN 7, VLAN 8, and VLAN 9.

[0142] Step 705: UPF sends a data packet through the first session.

[0143] That is, the UPF sends the received data packet through the first session corresponding to the received data packet. Alternatively, it can be understood that the UPF sends the data packet to the terminal to which the first session belongs through the first session.

[0144] Through steps 701 to 705, the SMF obtains the correspondence between the first session and the subnet information of the first subnet. The SMF then configures the correspondence between the first session and the subnet information of the first subnet for the UPF, so that the UPF can send the received multicast or broadcast packet through the corresponding session according to the IP subnet granularity. This method can achieve accurate data packet transmission.

[0145] To facilitate understanding of the technical solution of this application, the following four different specific embodiments are used to further illustrate the above technical solution. Figures 8 to 11 The embodiment is the above Figure 7 Specific implementation of the embodiment.

[0146] In the following examples, the first session is an IP-type PDU session or an Ethernet-type PDU session.

[0147] Figure 8 A schematic diagram of a wireless communication method provided in an embodiment of the present application. The method includes the following steps:

[0148] Step 801: The terminal initiates a PDU session establishment process.

[0149] Step 802: In the PDU session establishment process, the SMF sends an authentication and authorization request to the DN-AAA server. Correspondingly, the DN-AAA server receives the authentication and authorization request.

[0150] The authentication / authorization request may carry the GPSI and request ID of the terminal.

[0151] Step 803: The DN-AAA server sends an authentication and authorization reply to the SMF. Correspondingly, the SMF receives the authentication and authorization reply.

[0152] The authentication and authorization reply carries the authentication and authorization result, IP address configuration information, and request ID. The IP address configuration information includes the IP address and IP subnet mask of the PDU session.

[0153] The SMF stores the correspondence between the PDU session identifier and the request ID. Therefore, based on the request ID in the authentication and authorization reply, the SMF can determine that the IP address configuration information in the authentication and authorization reply corresponds to the PDU session. The SMF then determines the subnet information for the IP address based on the IP address configuration information. This subnet information is the subnet information for the IP subnet corresponding to the PDU session.

[0154] Step 804: The SMF sends an N4 session establishment / modification request to the UPF. Accordingly, the UPF receives the N4 session establishment / modification request.

[0155] The N4 session establishment / modification request carries a PDR, which includes the subnet information of the IP subnet corresponding to the PDU session. Since one PDR corresponds to one PDU session, the subnet information included in the PDR of a PDU session is the subnet information corresponding to the PDU session.

[0156] It should be noted that when the subnet information in the PDR includes the IP network number and IP subnet number of the PDU session, the UPF can determine the IP subnet mask based on the IP network number and IP subnet number.

[0157] Step 805: UPF processes the received data packet according to the PDR.

[0158] As an implementation method, UPF obtains the destination IP address in the received data packet and determines whether the data packet is a multicast packet or a broadcast packet within the subnet. If the data packet is a multicast packet or a broadcast packet within the subnet, UPF obtains the source IP address of the data packet, and then performs an AND operation on the source IP address and the subnet mask of the PDU session to derive the IP network number and IP subnet number corresponding to the source IP address of the data packet. Then, the IP network number and IP subnet number corresponding to the source IP address are compared with the IP network number and IP subnet number of the PDU session respectively. If the IP network number corresponding to the source IP address is the same as the IP network number of the PDU session, and the IP subnet number corresponding to the source IP address is the same as the subnet number of the PDU session, the data packet is copied and forwarded to the PDU session. If the IP network number corresponding to the source IP address is different from the IP network number of the PDU session or the IP subnet number corresponding to the source IP address is different from the subnet number of the PDU session, the data packet is not forwarded on the PDU session.

[0159] For example, the IP addresses of PDU Session 1 and PDU Session 2 of Terminal 1 are 140.252.255.1 and 140.252.255.2, respectively; the IP addresses of PDU Session 3 and PDU Session 4 of Terminal 2 are 140.252.255.3 and 140.252.255.4, respectively; and the IP addresses of PDU Session 5 and PDU Session 6 of Terminal 3 are 140.252.254.1 and 140.252.254.2, respectively. Furthermore, the subnet masks of these PDU sessions are all 255.255.255.0. When the SMF configures the PDR to the UPF, each PDR includes the subnet information of the IP subnet corresponding to a PDU session. For example, PDR1 includes 140.252.255.1 and 255.255.255.0, and PDR1 corresponds to PDU session 1. PDR2 includes 140.252.255.2 and 255.255.255.0, and PDR2 corresponds to PDU session 2. PDR3 includes 140.252.255.3 and 255.255.255.0, and PDR3 corresponds to PDU session 2. In session 3, PDR4 includes 140.252.255.4 and 255.255.255.0, and PDR4 corresponds to PDU session 4. PDR5 includes 140.252.254.1 and 255.255.255.0, and PDR5 corresponds to PDU session 5. PDR6 includes 140.252.254.2 and 255.255.255.0, and PDR6 corresponds to PDU session 6.

[0160] When the UPF receives a data packet, it first determines whether it is a multicast packet or a broadcast packet based on the packet's destination IP address. For example, if the destination IP address is one of 224.0.0.0 to 239.255.255.255, the packet is determined to be a multicast packet. If the destination IP address is one of the four broadcast IP addresses described above, the packet is determined to be a broadcast packet. If the packet is determined to be a multicast packet or a broadcast packet, the source IP address of the packet is obtained and then matched with the aforementioned PDR.

[0161] For example, if the source IP address is 140.252.255.5, then first perform an AND operation on 140.252.255.5 and the subnet mask 255.255.255.0 in PDR1 to obtain the IP network number 140.252 and IP subnet number 255 corresponding to the source IP address. Then, the IP network number (i.e., 140.252) and IP subnet number (i.e., 255) corresponding to the source IP address are compared with the IP network number and IP subnet number of the IP subnet information in PDR1. If they are the same, then it is determined that the source IP address matches the PDU session 1 corresponding to PDR1, and the data packet is forwarded to the PDU session 1 corresponding to PDR1. Similarly, the UPF also forwards the data packet to the PDU session 2 corresponding to PDR2, the PDU session 3 corresponding to PDR3, and the PDU session 4 corresponding to PDR4.

[0162] For example, if the source IP address is 140.252.254.3, then the AND operation is first performed on 140.252.254.3 and the subnet mask 255.255.255.0 in PDR1 to obtain the IP network number 140.252 and IP subnet number 254 corresponding to the source IP address. Then, the IP network number (i.e., 140.252) and IP subnet number (i.e., 254) corresponding to the source IP address are compared with the IP network number and IP subnet number of the IP subnet information in PDR1 to determine that the IP subnet numbers are different. It is then determined that the source IP address does not match the PDU session 1 corresponding to PDR1, and the data packet is not forwarded to the PDU session 1 corresponding to PDR1. Similarly, the UPF does not forward the data packet to the PDU session 2 corresponding to PDR2, the PDU session 3 corresponding to PDR3, and the PDU session 4 corresponding to PDR4. However, the UPF determines that the source IP address matches the PDU session 5 corresponding to PDR5 and the PDU session 6 corresponding to PDR6, and then the UPF forwards the data packet to the PDU session 5 corresponding to PDR5 and the PDU session 6 corresponding to PDR6.

[0163] As another implementation method, UPF obtains the destination IP address in the received data packet and determines whether the data packet is a multicast packet or a broadcast packet within the subnet. If the data packet is a multicast packet or a broadcast packet within the subnet, UPF obtains the source IP address of the data packet, and then performs an AND operation on the source IP address and the subnet mask of the PDU session to derive the subnet information corresponding to the source IP address of the data packet. Then, the subnet information corresponding to the source IP address is compared with the subnet information corresponding to the PDU session. If the subnet information corresponding to the source IP address is the same as the subnet information corresponding to the PDU session, the data packet is copied and forwarded to the PDU session. If the subnet information corresponding to the source IP address is different from the subnet information corresponding to the PDU session, the data packet is not forwarded on the PDU session. This method does not distinguish between the IP network number and the IP subnet number in a subnet information separately, but takes the subnet information corresponding to the source IP address as a whole, and the subnet information corresponding to the PDU session as a whole, and compares the two subnet information. As an example, if the source IP address is 140.252.255.5, then first perform an AND operation on 140.252.255.5 and the subnet mask 255.255.255.0 in the PDR1 in the above example, and obtain the subnet information corresponding to the source IP address as 140.252.255.0 / 24. Then compare the subnet information corresponding to the source IP address (i.e. 140.252.255.0 / 24) with the subnet information corresponding to PDR1 (i.e. 140.252.255.0 / 24), and determine that the two are the same. Then, it is determined that the source IP address matches the PDU session 1 corresponding to PDR1, and the data packet is forwarded to the PDU session 1 corresponding to PDR1. Similarly, the UPF also forwards the data packet to the PDU session 2 corresponding to PDR2, the PDU session 3 corresponding to PDR3, and the PDU session 4 corresponding to PDR4.

[0164] In the above embodiment, the SMF obtains the correspondence between the subnet information of the IP subnet and the PDU session based on the subnet information of the IP subnet corresponding to the PDU session of the terminal provided by the DN-AAA server, and then the SMF configures the correspondence between the subnet information of the IP subnet and the PDU session to the UPF through the PDR, so that the UPF can send the received multicast packet or broadcast packet to the corresponding PDU session according to the IP subnet granularity.

[0165] Figure 9 A schematic diagram of a wireless communication method provided in an embodiment of the present application. The method includes the following steps:

[0166] Step 901: The terminal completes the PDU session establishment process.

[0167] Step 902: The terminal obtains IP configuration information, including the IP address and IP subnet mask of the PDU session.

[0168] For example, a DN-AAA server or a DHCP server may allocate an IP address to the terminal and send the IP configuration information to the terminal.

[0169] Step 903: The terminal sends the subnet information of the IP subnet corresponding to the PDU session to the SMF. Correspondingly, the SMF receives the subnet information of the IP subnet corresponding to the PDU session.

[0170] The subnet information includes an IP address and an IP subnet mask, or an IP network number and an IP subnet number.

[0171] Steps 904 to 905 are the same as steps 804 to 805 above, and reference may be made to the above description.

[0172] In the above embodiment, the SMF obtains the correspondence between the subnet information of the IP subnet and the PDU session based on the subnet information of the IP subnet corresponding to the PDU session provided by the terminal, and then the SMF configures the correspondence between the subnet information of the IP subnet and the PDU session to the UPF through the PDR, so that the UPF can send the received multicast packet or broadcast packet to the corresponding PDU session according to the IP subnet granularity.

[0173] Figure 10 A schematic diagram of a wireless communication method provided in an embodiment of the present application. The method includes the following steps:

[0174] Step 1001: The terminal initiates a PDU session establishment process.

[0175] The PDU session may be an Ethernet type PDU session.

[0176] Step 1002: The SMF sends an N4 session establishment / modification request to the UPF, which carries indication information. Accordingly, the UPF receives the N4 session establishment / modification request.

[0177] For example, the indication information may instruct the UPF to detect packets that configure IP information for the terminal. Alternatively, the indication information is used to request configuration information for an IP address. Alternatively, the indication information may include the MAC address of the terminal's PDU session, thereby instructing the UPF to detect packets containing the MAC address. It should be noted that the SMF only sends the above indication information to the UPF for PDU sessions that require allocation of IP addresses. The indication information may, for example, be information in a specific field in an N4 session establishment / modification request.

[0178] Step 1003: The UPF detects a data packet configuring IP information for the terminal session according to the indication information.

[0179] For example, a terminal requests a DHCP server to allocate an IP address through the UPF. The DHCP server allocates an IP address to the terminal based on the terminal's request and sends a DHCP response to the terminal through the UPF. The DHCP response carries the configuration information of the IP address (or IP information). The UPF can detect the data packet that configures the IP information for the terminal's session based on the indication information, that is, the data packet that carries the DHCP response.

[0180] After the UPF detects the data packet that configures the IP information for the terminal session, it can obtain the IP information from the data packet. The IP information includes, for example, the IP address and IP subnet mask of the PDU session.

[0181] Step 1004: UPF sends an N4 report to SMF, which carries IP information. Accordingly, SMF receives the N4 report.

[0182] Since the N4 report and the PDU session are in a one-to-one correspondence, when the IP information is sent to the SMF through an N4 report, the SMF can determine the correspondence between the PDU session and the IP information based on the N4 report and the IP information in the N4 report.

[0183] Step 1005: The SMF sends an N4 report response to the UPF. Accordingly, the UPF receives the N4 report response.

[0184] This step is optional.

[0185] Step 1006: The SMF sends an N4 session modification request to the UPF. Accordingly, the UPF receives the N4 session modification request.

[0186] The N4 session modification request carries one or more PDRs, each of which includes subnet information of the IP subnet corresponding to the PDU session.

[0187] It should be noted that when the subnet information in the PDR includes the IP network number and IP subnet number of the PDU session, the UPF can determine the IP subnet mask based on the IP network number and IP subnet number.

[0188] Step 1007 is the same as the aforementioned step 805, and reference may be made to the aforementioned description.

[0189] In the above embodiment, SMF instructs UPF to detect the data packet that configures IP information for the terminal, and obtains the correspondence between the subnet information of the IP subnet and the PDU session based on the IP information reported by UPF through the N4 report corresponding to the PDU session. Then, SMF configures the correspondence between the subnet information of the IP subnet and the PDU session to UPF through PDR, so that UPF can send the received multicast packet or broadcast packet to the corresponding PDU session according to the IP subnet granularity.

[0190] Figure 11 A schematic diagram of a wireless communication method provided in an embodiment of the present application. The method includes the following steps:

[0191] Step 1101: The terminal initiates a PDU session establishment process.

[0192] The PDU session may be an Ethernet type PDU session.

[0193] Step 1102: The SMF sends an authentication and authorization request to the DN-AAA server. Correspondingly, the DN-AAA server receives the authentication and authorization request.

[0194] Step 1103: The DN-AAA server sends an authentication and authorization reply to the SMF. Accordingly, the SMF receives the authentication and authorization reply.

[0195] The authentication and authorization reply carries the allowed MAC address list, allowed VLAN list, and matching VLAN list corresponding to the PDU session.

[0196] The allowed MAC address list includes one or more MAC addresses.

[0197] The allowed VLAN list includes one or more VLAN identifiers (such as VLAN IDs) that the terminal is allowed to use. When the allowed VLAN list includes multiple VLAN identifiers, the IP addresses of the PDU sessions of the terminals in the multiple VLANs correspond to the same IP subnet, that is, one allowed VLAN list corresponds to one IP subnet.

[0198] The matching VLAN list includes identifiers (such as VLAN IDs) of all VLANs in an IP subnet, and the IP subnet is the IP subnet corresponding to the allowed VLAN list.

[0199] The relationship between the matching VLAN list and the allowed VLAN list is as follows: the VLAN ID in the allowed VLAN list is a part of the VLAN ID in the matching VLAN list, or the VLAN ID in the allowed VLAN list is the same as the VLAN ID in the matching VLAN list. Figure 6For example, assuming that the allowed VLAN list includes VLAN ID 1, the matching VLAN list includes VLAN ID 1, VLAN ID 2, VLAN ID 3, and VLAN ID 4. For another example, assuming that the allowed VLAN list includes VLAN ID 7 and VLAN ID 8, the matching VLAN list includes VLAN ID 7, VLAN ID 8, and VLAN ID 9.

[0200] The SMF may send the allowed MAC address list and the allowed VLAN list to the terminal, so that the terminal selects a MAC address from the allowed MAC address list for use and selects a VLAN from the allowed VLAN list for use.

[0201] Step 1104: SMF sends an N4 session establishment / modification request to UPF. Accordingly, UPF receives the N4 session establishment / modification request.

[0202] The N4 session establishment / modification request carries a PDR, which includes a matching VLAN list corresponding to the PDU session.

[0203] Step 1105: UPF processes the received data packet according to the PDR.

[0204] The UPF obtains the destination MAC address in the received data packet and determines whether the data packet is a multicast packet or a broadcast packet. If the data packet is a multicast packet or a broadcast packet, the UPF detects the EtherType field of the data packet and, based on the value of the EtherType field, determines that the data packet is an IP data packet based on Ethernet type services. The UPF then obtains the destination IP address of the data packet and, based on the destination IP address, determines whether the data packet is a multicast packet or a broadcast packet within the subnet. If the data packet is a multicast packet or a broadcast packet within the subnet, the UPF obtains the VLAN ID from the data packet. If it is determined that the VLAN ID belongs to the matching VLAN ID list in the PDR, the UPF copies and forwards the data packet to the PDU session corresponding to the PDR. Otherwise, the data packet is not forwarded on the PDU session.

[0205] In the above embodiment, SMF configures the matching VLAN list corresponding to the PDU session to UPF through PDR based on the matching VLAN list corresponding to the PDU session provided by the DN-AAA server. One matching VLAN list corresponds to one IP subnet, so that UPF can send the received multicast packet or broadcast packet to the corresponding PDU session according to the IP subnet granularity.

[0206] It is understood that to implement the functions described in the above embodiments, the UPF, SMF, DN-AAA, and terminal include hardware structures and / or software modules corresponding to the respective functions. Those skilled in the art will readily appreciate that, in conjunction with the various exemplary units and method steps described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0207] Figure 12 and Figure 13 Schematic diagram of the structure of possible communication devices provided for embodiments of the present application. These communication devices can be used to implement the functions of the terminal, UPF, SMF or DN-AAA in the above-mentioned method embodiments, and thus can also achieve the beneficial effects possessed by the above-mentioned method embodiments. In the embodiments of the present application, the communication device can be a terminal as shown in Figure 1(a) or Figure 1(b), or a UPF as shown in Figure 1(a) or Figure 1(b), or an SMF as shown in Figure 1(a) or Figure 1(b), or a module (such as a chip) applied to a terminal, UPF or SMF, or a DN-AAA or a module (such as a chip) applied to a DN-AAA.

[0208] like Figure 12 As shown, the communication device 1200 includes a processing unit 1210 and a transceiver unit 1220. The communication device 1200 is used to implement the above Figure 5 、 Figures 8 to 11 The method embodiment shown in FIG. 1 is a function of a terminal, a UPF, a SMF or a DN-AAA.

[0209] When the communication device 1200 is used to implement Figure 5 、 Figures 8 to 11 The functions of the UPF in the method embodiment shown are: a transceiver unit 1220, used to receive a data packet, which is a multicast packet or a broadcast packet; sending the data packet through a first session; a processing unit 1210, used to obtain subnet information of the first subnet corresponding to the first session; and determining, based on the subnet information, that the data packet corresponds to the first session in the first subnet.

[0210] In one possible implementation method, the processing unit 1210 is specifically configured to determine the subnet information corresponding to the source IP address in the data packet; if the subnet information corresponding to the first session is the same as the subnet information corresponding to the source IP address, then the data packet is determined to correspond to the first session.

[0211] In a possible implementation method, the processing unit 1210 is specifically configured to receive a packet detection rule from a session management network element through the transceiver unit 1220 , where the packet detection rule includes the subnet information.

[0212] In a possible implementation method, the transceiver unit 1220 is further used to receive indication information from the session management network element; send IP information to the session management network element, and the IP information is used to determine the subnet information; the processing unit 1210 is further used to detect the data packet configuring IP information for the first session based on the indication information, wherein the data packet configuring IP information for the first session includes the IP information corresponding to the first session, and the first session is an Ethernet type session.

[0213] In one possible implementation method, the processing unit 1210 is specifically configured to obtain an identifier of a first VLAN in the data packet; obtain a VLAN set, where the VLAN set includes one or more VLANs under the first subnet; and determine that the data packet corresponds to the first session if the first VLAN belongs to the VLAN set.

[0214] In a possible implementation method, the processing unit 1210 is specifically configured to receive, through the transceiver unit 1220 , a packet detection rule from a session management network element, where the packet detection rule includes the VLAN set.

[0215] When the communication device 1200 is used to implement Figure 5 、 Figures 8 to 11 The functions of SMF in the method embodiment shown are: processing unit 1210, used to obtain subnet information of the first subnet corresponding to the first session; transceiver unit 1220, used to send the subnet information to the user plane network element, and the subnet information is used to detect data packets matching the subnet information.

[0216] In a possible implementation method, the transceiver unit 1220 is specifically configured to send a packet detection rule to a user plane network element, where the packet detection rule includes the subnet information.

[0217] In one possible implementation method, the processing unit 1210 is specifically used to send indication information to the user plane network element through the transceiver unit 1220, where the indication information indicates the detection of a data packet configuring IP information for the first session, where the first session is an Ethernet type session; receive the IP information corresponding to the first session from the user plane network element through the transceiver unit 1220; and determine the subnet information based on the IP information.

[0218] In a possible implementation method, the processing unit 1210 is specifically configured to receive the subnet information from the authentication, authorization and accounting server through the transceiver unit 1220 .

[0219] In a possible implementation method, the transceiver unit 1220 is further configured to request the subnet information from the authentication, authorization and accounting server.

[0220] In a possible implementation method, the processing unit 1210 is specifically configured to receive the subnet information from the terminal through the transceiver unit 1220 .

[0221] When the communication device 1200 is used to implement Figure 5 、 Figures 8 to 11 The functions of the terminal in the method embodiment shown are: a processing unit 1210, used to obtain subnet information of the first subnet corresponding to the first session; a transceiver unit 1220, used to send the subnet information to the session management network element, and the subnet information is used to detect data packets matching the subnet information.

[0222] In a possible implementation method, the processing unit 1210 is specifically configured to receive the subnet information from the authentication, authorization and accounting server or the DHCP server through the transceiver unit 1220 .

[0223] When the communication device 1200 is used to implement Figure 5 、 Figures 8 to 11 The functions of DN-AAA in the method embodiment shown are: a processing unit 1210, configured to obtain subnet information of a first subnet corresponding to a first session; and a transceiver unit 1220, configured to send the subnet information to a session management network element, where the subnet information is used to detect data packets matching the subnet information.

[0224] For more detailed description of the processing unit 1210 and the transceiver unit 1220, please refer to Figure 5 、 Figures 8 to 11 The relevant description in the method embodiment shown is directly obtained and will not be repeated here.

[0225] like Figure 13 As shown, communication device 1300 includes a processor 1310 and an interface circuit 1320. Processor 1310 and interface circuit 1320 are coupled to each other. It will be appreciated that interface circuit 1320 may be a transceiver or an input / output interface. Optionally, communication device 1300 may further include a memory 1330 for storing instructions executed by processor 1310, input data required by processor 1310 to execute instructions, or data generated after processor 1310 executes instructions.

[0226] When the communication device 1300 is used to implement Figure 5 、 Figures 8 to 11 When the method shown is used, the processor 1310 is used to implement the functions of the above-mentioned processing unit 1210, and the interface circuit 1320 is used to implement the functions of the above-mentioned transceiver unit 1220.

[0227] When the communication device is a chip used in a terminal, the chip implements the functions of the terminal in the above method embodiments. The chip receives information from other modules in the terminal (such as a radio frequency module or antenna), which is sent by the base station to the terminal; or the chip sends information to other modules in the terminal (such as a radio frequency module or antenna), which is sent by the terminal to the base station.

[0228] When the communication device is a chip used in a UPF, the chip implements the UPF functionality described in the method embodiments. The chip receives information from other modules in the UPF, which is information sent to the UPF by other devices; or the chip sends information to other modules in the UPF, which is information sent to other devices by the UPF.

[0229] When the communication device is a chip used in an SMF, the chip implements the SMF functions described in the method embodiments. The chip receives information from other modules in the SMF, where the information is sent to the SMF by other devices; or the chip sends information to other modules in the SMF, where the information is sent to other devices by the SMF.

[0230] When the communication device is a chip used in a DN-AAA, the chip implements the DN-AAA functions described in the method embodiments. The chip receives information from other modules in the DN-AAA, which is information sent to the DN-AAA by other devices; or sends information to other modules in the DN-AAA, which is information sent to other devices by the DN-AAA.

[0231] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0232] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC.

[0233] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a base station, a user equipment, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0234] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0235] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next related objects are in an "or" relationship; in the formulas of this application, the character " / " indicates that the previous and next related objects are in a "division" relationship.

[0236] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A wireless communication method, characterized in that: include: Obtaining subnet information of a first subnet corresponding to the first session; receiving a data packet, wherein the data packet is a multicast packet or a broadcast packet; Determining subnet information corresponding to a source Internet Protocol (IP) address in the data packet; If the subnet information corresponding to the first session is the same as the subnet information corresponding to the source IP address, determining that the data packet corresponds to the first session in the first subnet; The data packet is sent through the first session.

2. The method according to claim 1, wherein The obtaining of subnet information of the first subnet corresponding to the first session includes: A packet detection rule is received from a session management network element, where the packet detection rule includes the subnet information.

3. The method according to claim 2, wherein Also includes: receiving instruction information from the session management network element; detecting, according to the indication information, a data packet for configuring IP information for the first session, wherein the data packet for configuring IP information for the first session includes IP information corresponding to the first session, and the first session is an Ethernet-type session; The IP information is sent to the session management network element, where the IP information is used to determine the subnet information.

4. A wireless communication method, characterized in that: include: Obtaining subnet information of a first subnet corresponding to the first session; receiving a data packet, where the data packet is a multicast packet or a broadcast packet; Obtaining an identifier of a first virtual local area network VLAN in the data packet; Obtain a VLAN set, where the VLAN set includes one or more VLANs under the first subnet; If the first VLAN belongs to the VLAN set, determining that the data packet corresponds to the first session in the first subnet; The data packet is sent through the first session.

5. The method according to claim 4, wherein The obtaining of the VLAN set includes: A packet detection rule is received from a session management network element, where the packet detection rule includes the VLAN set.

6. A communication device, characterized in that: include: a transceiver unit, configured to receive a data packet, wherein the data packet is a multicast packet or a broadcast packet; and send the data packet via a first session; a processing unit, configured to obtain subnet information of a first subnet corresponding to the first session; Determining subnet information corresponding to a source Internet Protocol (IP) address in the data packet; If the subnet information corresponding to the first session is the same as the subnet information corresponding to the source IP address, it is determined that the data packet corresponds to the first session in the first subnet.

7. The device according to claim 6, characterized in that The processing unit is specifically configured to receive a packet detection rule from a session management network element through the transceiver unit, where the packet detection rule includes the subnet information.

8. The device according to claim 7, wherein The transceiver unit is further configured to receive instruction information from the session management network element; and send IP information to the session management network element, wherein the IP information is used to determine the subnet information; The processing unit is further configured to detect, based on the indication information, a data packet configuring IP information for the first session, wherein the data packet configuring IP information for the first session includes the IP information corresponding to the first session, and the first session is an Ethernet type session.

9. A communication device, characterized in that: include: a transceiver unit, configured to receive a data packet, wherein the data packet is a multicast packet or a broadcast packet; and send the data packet via a first session; a processing unit, configured to obtain subnet information of a first subnet corresponding to the first session; Obtaining an identifier of a first VLAN in the data packet; Obtain a VLAN set, where the VLAN set includes one or more VLANs under the first subnet; If the first VLAN belongs to the VLAN set, it is determined that the data packet corresponds to the first session in the first subnet.

10. The device according to claim 9, wherein The processing unit is specifically configured to receive a packet detection rule from a session management network element through the transceiver unit, where the packet detection rule includes the VLAN set.

11. A communication device, characterized in that: The method comprises a module for executing the method according to any one of claims 1 to 3, or a module for executing the method according to claim 4 or 5.

12. A communication device, characterized in that: The method comprises a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method according to any one of claims 1 to 3 or the method according to claim 4 or 5 through a logic circuit or executing code instructions.

13. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 5 is implemented.

Images